#[non_exhaustive]
pub enum CreatePipelineErrorKind {
ConcurrentModificationException(ConcurrentModificationException),
InvalidActionDeclarationException(InvalidActionDeclarationException),
InvalidBlockerDeclarationException(InvalidBlockerDeclarationException),
InvalidStageDeclarationException(InvalidStageDeclarationException),
InvalidStructureException(InvalidStructureException),
InvalidTagsException(InvalidTagsException),
LimitExceededException(LimitExceededException),
PipelineNameInUseException(PipelineNameInUseException),
TooManyTagsException(TooManyTagsException),
ValidationException(ValidationException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreatePipeline
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
ConcurrentModificationException(ConcurrentModificationException)
Unable to modify the tag due to a simultaneous update request.
InvalidActionDeclarationException(InvalidActionDeclarationException)
The action declaration was specified in an invalid format.
InvalidBlockerDeclarationException(InvalidBlockerDeclarationException)
Reserved for future use.
InvalidStageDeclarationException(InvalidStageDeclarationException)
The stage declaration was specified in an invalid format.
InvalidStructureException(InvalidStructureException)
The structure was specified in an invalid format.
InvalidTagsException(InvalidTagsException)
The specified resource tags are invalid.
LimitExceededException(LimitExceededException)
The number of pipelines associated with the AWS account has exceeded the limit allowed for the account.
PipelineNameInUseException(PipelineNameInUseException)
The specified pipeline name is already in use.
TooManyTagsException(TooManyTagsException)
The tags limit for a resource has been exceeded.
ValidationException(ValidationException)
The validation 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.