Enum aws_sdk_ecr::error::CreateRepositoryErrorKind

#[non_exhaustive]
pub enum CreateRepositoryErrorKind {
    InvalidParameterException(InvalidParameterException),
    InvalidTagParameterException(InvalidTagParameterException),
    KmsException(KmsException),
    LimitExceededException(LimitExceededException),
    RepositoryAlreadyExistsException(RepositoryAlreadyExistsException),
    ServerException(ServerException),
    TooManyTagsException(TooManyTagsException),
    Unhandled(Unhandled),
}

Types of errors that can occur for the CreateRepository operation.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

InvalidParameterException(InvalidParameterException)

The specified parameter is invalid. Review the available parameters for the API request.

InvalidTagParameterException(InvalidTagParameterException)

An invalid parameter has been specified. Tag keys can have a maximum character length of 128 characters, and tag values can have a maximum length of 256 characters.

KmsException(KmsException)

The operation failed due to a KMS exception.

LimitExceededException(LimitExceededException)

The operation did not 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.

RepositoryAlreadyExistsException(RepositoryAlreadyExistsException)

The specified repository already exists in the specified registry.

ServerException(ServerException)

These errors are usually caused by a server-side issue.

TooManyTagsException(TooManyTagsException)

The list of tags on the repository is over the limit. The maximum number of tags that can be applied to a repository is 50.

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.

Trait Implementations

impl Debug for CreateRepositoryErrorKind

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.