#[non_exhaustive]
pub enum UploadLayerPartErrorKind {
InvalidLayerPartException(InvalidLayerPartException),
InvalidParameterException(InvalidParameterException),
LimitExceededException(LimitExceededException),
RegistryNotFoundException(RegistryNotFoundException),
RepositoryNotFoundException(RepositoryNotFoundException),
ServerException(ServerException),
UnsupportedCommandException(UnsupportedCommandException),
UploadNotFoundException(UploadNotFoundException),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the UploadLayerPart operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
InvalidLayerPartException(InvalidLayerPartException)
The layer part size isn't valid, or the first byte specified isn't consecutive to the last byte of a previous layer part upload.
InvalidParameterException(InvalidParameterException)
The specified parameter is invalid. Review the available parameters for the API request.
LimitExceededException(LimitExceededException)
The operation didn't succeed because it would have exceeded a service limit for your account. For more information, see Amazon ECR Service Quotas in the Amazon Elastic Container Registry User Guide.
RegistryNotFoundException(RegistryNotFoundException)
The registry doesn't exist.
RepositoryNotFoundException(RepositoryNotFoundException)
The specified repository can't be found. Check the spelling of the specified repository and ensure that you're performing operations on the correct registry.
ServerException(ServerException)
These errors are usually caused by a server-side issue.
UnsupportedCommandException(UnsupportedCommandException)
The action isn't supported in this Region.
UploadNotFoundException(UploadNotFoundException)
The upload can't be found, or the specified upload ID isn't 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.