#[non_exhaustive]
pub enum DeleteConformancePackErrorKind {
NoSuchConformancePackException(NoSuchConformancePackException),
ResourceInUseException(ResourceInUseException),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the DeleteConformancePack operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
NoSuchConformancePackException(NoSuchConformancePackException)
You specified one or more conformance packs that do not exist.
ResourceInUseException(ResourceInUseException)
You see this exception in the following cases:
-
For DeleteConfigRule, Config is deleting this rule. Try your request again later.
-
For DeleteConfigRule, the rule is deleting your evaluation results. Try your request again later.
-
For DeleteConfigRule, a remediation action is associated with the rule and Config cannot delete this rule. Delete the remediation action associated with the rule before deleting the rule and try your request again later.
-
For PutConfigOrganizationRule, organization Config rule deletion is in progress. Try your request again later.
-
For DeleteOrganizationConfigRule, organization Config rule creation is in progress. Try your request again later.
-
For PutConformancePack and PutOrganizationConformancePack, a conformance pack creation, update, and deletion is in progress. Try your request again later.
-
For DeleteConformancePack, a conformance pack creation, update, and deletion is in progress. Try your request again later.
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.