#[non_exhaustive]
pub enum CreateOpsMetadataErrorKind {
InternalServerError(InternalServerError),
OpsMetadataAlreadyExistsException(OpsMetadataAlreadyExistsException),
OpsMetadataInvalidArgumentException(OpsMetadataInvalidArgumentException),
OpsMetadataLimitExceededException(OpsMetadataLimitExceededException),
OpsMetadataTooManyUpdatesException(OpsMetadataTooManyUpdatesException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateOpsMetadata
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
InternalServerError(InternalServerError)
An error occurred on the server side.
OpsMetadataAlreadyExistsException(OpsMetadataAlreadyExistsException)
An OpsMetadata object already exists for the selected resource.
OpsMetadataInvalidArgumentException(OpsMetadataInvalidArgumentException)
One of the arguments passed is invalid.
OpsMetadataLimitExceededException(OpsMetadataLimitExceededException)
Your account reached the maximum number of OpsMetadata objects allowed by Application Manager. The maximum is 200 OpsMetadata objects. Delete one or more OpsMetadata object and try again.
OpsMetadataTooManyUpdatesException(OpsMetadataTooManyUpdatesException)
The system is processing too many concurrent updates. Wait a few moments and try again.
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.