#[non_exhaustive]
pub enum CompleteLayerUploadErrorKind {
EmptyUploadException(EmptyUploadException),
InvalidLayerException(InvalidLayerException),
InvalidParameterException(InvalidParameterException),
KmsException(KmsException),
LayerAlreadyExistsException(LayerAlreadyExistsException),
LayerPartTooSmallException(LayerPartTooSmallException),
RepositoryNotFoundException(RepositoryNotFoundException),
ServerException(ServerException),
UploadNotFoundException(UploadNotFoundException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CompleteLayerUpload
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
EmptyUploadException(EmptyUploadException)
The specified layer upload does not contain any layer parts.
InvalidLayerException(InvalidLayerException)
The layer digest calculation performed by Amazon ECR upon receipt of the image layer does not match the digest specified.
InvalidParameterException(InvalidParameterException)
The specified parameter is invalid. Review the available parameters for the API request.
KmsException(KmsException)
The operation failed due to a KMS exception.
LayerAlreadyExistsException(LayerAlreadyExistsException)
The image layer already exists in the associated repository.
LayerPartTooSmallException(LayerPartTooSmallException)
Layer parts must be at least 5 MiB in size.
RepositoryNotFoundException(RepositoryNotFoundException)
The specified repository could not be found. Check the spelling of the specified repository and ensure that you are performing operations on the correct registry.
ServerException(ServerException)
These errors are usually caused by a server-side issue.
UploadNotFoundException(UploadNotFoundException)
The upload could not be found, or the specified upload ID is not valid for this repository.
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.