#[non_exhaustive]
pub enum ListDeploymentTargetsErrorKind {
DeploymentDoesNotExistException(DeploymentDoesNotExistException),
DeploymentIdRequiredException(DeploymentIdRequiredException),
DeploymentNotStartedException(DeploymentNotStartedException),
InvalidDeploymentIdException(InvalidDeploymentIdException),
InvalidDeploymentInstanceTypeException(InvalidDeploymentInstanceTypeException),
InvalidInstanceStatusException(InvalidInstanceStatusException),
InvalidInstanceTypeException(InvalidInstanceTypeException),
InvalidNextTokenException(InvalidNextTokenException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the ListDeploymentTargets
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
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.
DeploymentNotStartedException(DeploymentNotStartedException)
The specified deployment has not started.
InvalidDeploymentIdException(InvalidDeploymentIdException)
At least one of the deployment IDs was specified in an invalid format.
InvalidDeploymentInstanceTypeException(InvalidDeploymentInstanceTypeException)
An instance type was specified for an in-place deployment. Instance types are supported for blue/green deployments only.
InvalidInstanceStatusException(InvalidInstanceStatusException)
The specified instance status does not exist.
InvalidInstanceTypeException(InvalidInstanceTypeException)
An invalid instance type was specified for instances in a blue/green deployment. Valid values include "Blue" for an original environment and "Green" for a replacement environment.
InvalidNextTokenException(InvalidNextTokenException)
The next token was specified in an invalid format.
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.