#[non_exhaustive]
pub enum CreateFieldLevelEncryptionProfileErrorKind {
FieldLevelEncryptionProfileAlreadyExists(FieldLevelEncryptionProfileAlreadyExists),
FieldLevelEncryptionProfileSizeExceeded(FieldLevelEncryptionProfileSizeExceeded),
InconsistentQuantities(InconsistentQuantities),
InvalidArgument(InvalidArgument),
NoSuchPublicKey(NoSuchPublicKey),
TooManyFieldLevelEncryptionEncryptionEntities(TooManyFieldLevelEncryptionEncryptionEntities),
TooManyFieldLevelEncryptionFieldPatterns(TooManyFieldLevelEncryptionFieldPatterns),
TooManyFieldLevelEncryptionProfiles(TooManyFieldLevelEncryptionProfiles),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateFieldLevelEncryptionProfile
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
FieldLevelEncryptionProfileAlreadyExists(FieldLevelEncryptionProfileAlreadyExists)
The specified profile for field-level encryption already exists.
FieldLevelEncryptionProfileSizeExceeded(FieldLevelEncryptionProfileSizeExceeded)
The maximum size of a profile for field-level encryption was exceeded.
InconsistentQuantities(InconsistentQuantities)
The value of Quantity
and the size of Items
don't match.
InvalidArgument(InvalidArgument)
An argument is invalid.
NoSuchPublicKey(NoSuchPublicKey)
The specified public key doesn't exist.
TooManyFieldLevelEncryptionEncryptionEntities(TooManyFieldLevelEncryptionEncryptionEntities)
The maximum number of encryption entities for field-level encryption have been created.
TooManyFieldLevelEncryptionFieldPatterns(TooManyFieldLevelEncryptionFieldPatterns)
The maximum number of field patterns for field-level encryption have been created.
TooManyFieldLevelEncryptionProfiles(TooManyFieldLevelEncryptionProfiles)
The maximum number of 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.