#[non_exhaustive]
pub enum PutLifecycleEventHookExecutionStatusErrorKind {
DeploymentDoesNotExistException(DeploymentDoesNotExistException),
DeploymentIdRequiredException(DeploymentIdRequiredException),
InvalidDeploymentIdException(InvalidDeploymentIdException),
InvalidLifecycleEventHookExecutionIdException(InvalidLifecycleEventHookExecutionIdException),
InvalidLifecycleEventHookExecutionStatusException(InvalidLifecycleEventHookExecutionStatusException),
LifecycleEventAlreadyCompletedException(LifecycleEventAlreadyCompletedException),
UnsupportedActionForDeploymentTypeException(UnsupportedActionForDeploymentTypeException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the PutLifecycleEventHookExecutionStatus
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.
InvalidDeploymentIdException(InvalidDeploymentIdException)
At least one of the deployment IDs was specified in an invalid format.
InvalidLifecycleEventHookExecutionIdException(InvalidLifecycleEventHookExecutionIdException)
A lifecycle event hook is invalid. Review the hooks
section in your AppSpec file to ensure the lifecycle events and hooks
functions are valid.
InvalidLifecycleEventHookExecutionStatusException(InvalidLifecycleEventHookExecutionStatusException)
The result of a Lambda validation function that verifies a lifecycle event is invalid. It should return Succeeded
or Failed
.
LifecycleEventAlreadyCompletedException(LifecycleEventAlreadyCompletedException)
An attempt to return the status of an already completed lifecycle event occurred.
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.