#[non_exhaustive]
pub enum DeleteDBClusterErrorKind {
DbClusterNotFoundFault(DbClusterNotFoundFault),
DbClusterSnapshotAlreadyExistsFault(DbClusterSnapshotAlreadyExistsFault),
InvalidDbClusterSnapshotStateFault(InvalidDbClusterSnapshotStateFault),
InvalidDbClusterStateFault(InvalidDbClusterStateFault),
SnapshotQuotaExceededFault(SnapshotQuotaExceededFault),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the DeleteDBCluster
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.
DbClusterNotFoundFault(DbClusterNotFoundFault)
DBClusterIdentifier
doesn't refer to an existing cluster.
DbClusterSnapshotAlreadyExistsFault(DbClusterSnapshotAlreadyExistsFault)
You already have a cluster snapshot with the given identifier.
InvalidDbClusterSnapshotStateFault(InvalidDbClusterSnapshotStateFault)
The provided value isn't a valid cluster snapshot state.
InvalidDbClusterStateFault(InvalidDbClusterStateFault)
The cluster isn't in a valid state.
SnapshotQuotaExceededFault(SnapshotQuotaExceededFault)
The request would cause you to exceed the allowed number of snapshots.
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.