#[non_exhaustive]
pub enum CreateFieldLevelEncryptionConfigErrorKind {
FieldLevelEncryptionConfigAlreadyExists(FieldLevelEncryptionConfigAlreadyExists),
InconsistentQuantities(InconsistentQuantities),
InvalidArgument(InvalidArgument),
NoSuchFieldLevelEncryptionProfile(NoSuchFieldLevelEncryptionProfile),
QueryArgProfileEmpty(QueryArgProfileEmpty),
TooManyFieldLevelEncryptionConfigs(TooManyFieldLevelEncryptionConfigs),
TooManyFieldLevelEncryptionContentTypeProfiles(TooManyFieldLevelEncryptionContentTypeProfiles),
TooManyFieldLevelEncryptionQueryArgProfiles(TooManyFieldLevelEncryptionQueryArgProfiles),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateFieldLevelEncryptionConfig
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
FieldLevelEncryptionConfigAlreadyExists(FieldLevelEncryptionConfigAlreadyExists)
The specified configuration for field-level encryption already exists.
InconsistentQuantities(InconsistentQuantities)
The value of Quantity
and the size of Items
don't match.
InvalidArgument(InvalidArgument)
An argument is invalid.
NoSuchFieldLevelEncryptionProfile(NoSuchFieldLevelEncryptionProfile)
The specified profile for field-level encryption doesn't exist.
QueryArgProfileEmpty(QueryArgProfileEmpty)
No profile specified for the field-level encryption query argument.
TooManyFieldLevelEncryptionConfigs(TooManyFieldLevelEncryptionConfigs)
The maximum number of configurations for field-level encryption have been created.
TooManyFieldLevelEncryptionContentTypeProfiles(TooManyFieldLevelEncryptionContentTypeProfiles)
The maximum number of content type profiles for field-level encryption have been created.
TooManyFieldLevelEncryptionQueryArgProfiles(TooManyFieldLevelEncryptionQueryArgProfiles)
The maximum number of query arg profiles for field-level encryption have been created.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.