#[non_exhaustive]
pub enum UpdatePipelineErrorKind {
AccessDeniedException(AccessDeniedException),
IncompatibleVersionException(IncompatibleVersionException),
InternalServiceException(InternalServiceException),
ResourceInUseException(ResourceInUseException),
ResourceNotFoundException(ResourceNotFoundException),
ValidationException(ValidationException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the UpdatePipeline
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
General authentication failure. The request was not signed correctly.
IncompatibleVersionException(IncompatibleVersionException)
InternalServiceException(InternalServiceException)
Elastic Transcoder encountered an unexpected exception while trying to fulfill the request.
ResourceInUseException(ResourceInUseException)
The resource you are attempting to change is in use. For example, you are attempting to delete a pipeline that is currently in use.
ResourceNotFoundException(ResourceNotFoundException)
The requested resource does not exist or is not available. For example, the pipeline to which you're trying to add a job doesn't exist or is still being created.
ValidationException(ValidationException)
One or more required parameter values were not provided in the request.
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.