#[non_exhaustive]
pub enum Error {
AccessDeniedException(AccessDeniedException),
ConcurrentModificationException(ConcurrentModificationException),
ConfigurationException(ConfigurationException),
InvalidNextTokenException(InvalidNextTokenException),
LimitExceededException(LimitExceededException),
ResourceAlreadyExistsException(ResourceAlreadyExistsException),
ResourceNotFoundException(ResourceNotFoundException),
ValidationException(ValidationException),
Unhandled(Unhandled),
}
Expand description
All possible error types for this service.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
AWS CodeStar Notifications can't create the notification rule because you do not have sufficient permissions.
ConcurrentModificationException(ConcurrentModificationException)
AWS CodeStar Notifications can't complete the request because the resource is being modified by another process. Wait a few minutes and try again.
ConfigurationException(ConfigurationException)
Some or all of the configuration is incomplete, missing, or not valid.
InvalidNextTokenException(InvalidNextTokenException)
The value for the enumeration token used in the request to return the next batch of the results is not valid.
LimitExceededException(LimitExceededException)
One of the AWS CodeStar Notifications limits has been exceeded. Limits apply to accounts, notification rules, notifications, resources, and targets. For more information, see Limits.
ResourceAlreadyExistsException(ResourceAlreadyExistsException)
A resource with the same name or ID already exists. Notification rule names must be unique in your Amazon Web Services account.
ResourceNotFoundException(ResourceNotFoundException)
AWS CodeStar Notifications can't find a resource that matches the provided ARN.
ValidationException(ValidationException)
One or more parameter values are not valid.
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.