Enum aws_sdk_docdb::error::DeleteDBInstanceErrorKind

#[non_exhaustive]
pub enum DeleteDBInstanceErrorKind {
    DbInstanceNotFoundFault(DbInstanceNotFoundFault),
    DbSnapshotAlreadyExistsFault(DbSnapshotAlreadyExistsFault),
    InvalidDbClusterStateFault(InvalidDbClusterStateFault),
    InvalidDbInstanceStateFault(InvalidDbInstanceStateFault),
    SnapshotQuotaExceededFault(SnapshotQuotaExceededFault),
    Unhandled(Unhandled),
}

Types of errors that can occur for the DeleteDBInstance operation.

Variants (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.

DbInstanceNotFoundFault(DbInstanceNotFoundFault)

DBInstanceIdentifier doesn't refer to an existing instance.

DbSnapshotAlreadyExistsFault(DbSnapshotAlreadyExistsFault)

DBSnapshotIdentifier is already being used by an existing snapshot.

InvalidDbClusterStateFault(InvalidDbClusterStateFault)

The cluster isn't in a valid state.

InvalidDbInstanceStateFault(InvalidDbInstanceStateFault)

The specified instance isn't in the available 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.

Trait Implementations

impl Debug for DeleteDBInstanceErrorKind

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.