#[non_exhaustive]
pub enum DescribeTaskSetsErrorKind {
AccessDeniedException(AccessDeniedException),
ClientException(ClientException),
ClusterNotFoundException(ClusterNotFoundException),
InvalidParameterException(InvalidParameterException),
ServerException(ServerException),
ServiceNotActiveException(ServiceNotActiveException),
ServiceNotFoundException(ServiceNotFoundException),
UnsupportedFeatureException(UnsupportedFeatureException),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the DescribeTaskSets operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
You don't have authorization to perform the requested action.
ClientException(ClientException)
These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource,. Or, it might be specifying an identifier that isn't valid.
ClusterNotFoundException(ClusterNotFoundException)
The specified cluster wasn't found. You can view your available clusters with ListClusters. Amazon ECS clusters are Region specific.
InvalidParameterException(InvalidParameterException)
The specified parameter isn't valid. Review the available parameters for the API request.
ServerException(ServerException)
These errors are usually caused by a server issue.
ServiceNotActiveException(ServiceNotActiveException)
The specified service isn't active. You can't update a service that's inactive. If you have previously deleted a service, you can re-create it with CreateService.
ServiceNotFoundException(ServiceNotFoundException)
The specified service wasn't found. You can view your available services with ListServices. Amazon ECS services are cluster specific and Region specific.
UnsupportedFeatureException(UnsupportedFeatureException)
The specified task isn't supported in this Region.
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.