#[non_exhaustive]
pub enum ContinueDeploymentErrorKind {
DeploymentAlreadyCompletedException(DeploymentAlreadyCompletedException),
DeploymentDoesNotExistException(DeploymentDoesNotExistException),
DeploymentIdRequiredException(DeploymentIdRequiredException),
DeploymentIsNotInReadyStateException(DeploymentIsNotInReadyStateException),
InvalidDeploymentIdException(InvalidDeploymentIdException),
InvalidDeploymentStatusException(InvalidDeploymentStatusException),
InvalidDeploymentWaitTypeException(InvalidDeploymentWaitTypeException),
UnsupportedActionForDeploymentTypeException(UnsupportedActionForDeploymentTypeException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the ContinueDeployment
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
DeploymentAlreadyCompletedException(DeploymentAlreadyCompletedException)
The deployment is already complete.
DeploymentDoesNotExistException(DeploymentDoesNotExistException)
The deployment with the IAM user or Amazon Web Services account does not exist.
DeploymentIdRequiredException(DeploymentIdRequiredException)
At least one deployment ID must be specified.
DeploymentIsNotInReadyStateException(DeploymentIsNotInReadyStateException)
The deployment does not have a status of Ready and can't continue yet.
InvalidDeploymentIdException(InvalidDeploymentIdException)
At least one of the deployment IDs was specified in an invalid format.
InvalidDeploymentStatusException(InvalidDeploymentStatusException)
The specified deployment status doesn't exist or cannot be determined.
InvalidDeploymentWaitTypeException(InvalidDeploymentWaitTypeException)
The wait type is invalid.
UnsupportedActionForDeploymentTypeException(UnsupportedActionForDeploymentTypeException)
A call was submitted that is not supported for the specified deployment type.
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.