#[non_exhaustive]
pub enum CreateDeploymentConfigErrorKind {
DeploymentConfigAlreadyExistsException(DeploymentConfigAlreadyExistsException),
DeploymentConfigLimitExceededException(DeploymentConfigLimitExceededException),
DeploymentConfigNameRequiredException(DeploymentConfigNameRequiredException),
InvalidComputePlatformException(InvalidComputePlatformException),
InvalidDeploymentConfigNameException(InvalidDeploymentConfigNameException),
InvalidMinimumHealthyHostValueException(InvalidMinimumHealthyHostValueException),
InvalidTrafficRoutingConfigurationException(InvalidTrafficRoutingConfigurationException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateDeploymentConfig
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
DeploymentConfigAlreadyExistsException(DeploymentConfigAlreadyExistsException)
A deployment configuration with the specified name with the IAM user or Amazon Web Services account already exists.
DeploymentConfigLimitExceededException(DeploymentConfigLimitExceededException)
The deployment configurations limit was exceeded.
DeploymentConfigNameRequiredException(DeploymentConfigNameRequiredException)
The deployment configuration name was not specified.
InvalidComputePlatformException(InvalidComputePlatformException)
The computePlatform is invalid. The computePlatform should be Lambda
, Server
, or ECS
.
InvalidDeploymentConfigNameException(InvalidDeploymentConfigNameException)
The deployment configuration name was specified in an invalid format.
InvalidMinimumHealthyHostValueException(InvalidMinimumHealthyHostValueException)
The minimum healthy instance value was specified in an invalid format.
InvalidTrafficRoutingConfigurationException(InvalidTrafficRoutingConfigurationException)
The configuration that specifies how traffic is routed during a deployment is invalid.
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.