#[non_exhaustive]
pub enum GetConformancePackComplianceDetailsErrorKind {
InvalidLimitException(InvalidLimitException),
InvalidNextTokenException(InvalidNextTokenException),
InvalidParameterValueException(InvalidParameterValueException),
NoSuchConfigRuleInConformancePackException(NoSuchConfigRuleInConformancePackException),
NoSuchConformancePackException(NoSuchConformancePackException),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the GetConformancePackComplianceDetails operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
InvalidLimitException(InvalidLimitException)
The specified limit is outside the allowable range.
InvalidNextTokenException(InvalidNextTokenException)
The specified next token is invalid. Specify the nextToken string that was returned in the previous response to get the next page of results.
InvalidParameterValueException(InvalidParameterValueException)
One or more of the specified parameters are invalid. Verify that your parameters are valid and try again.
NoSuchConfigRuleInConformancePackException(NoSuchConfigRuleInConformancePackException)
Config rule that you passed in the filter does not exist.
NoSuchConformancePackException(NoSuchConformancePackException)
You specified one or more conformance packs that do not exist.
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.