Class ErrorInformation
java.lang.Object
com.amazonaws.services.codedeploy.model.ErrorInformation
- All Implemented Interfaces:
Serializable
,Cloneable
Information about a deployment error.
- See Also:
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionclone()
boolean
getCode()
The error code:An accompanying error message.int
hashCode()
void
The error code:void
The error code:void
setMessage
(String message) An accompanying error message.toString()
Returns a string representation of this object; useful for testing and debugging.The error code:The error code:withMessage
(String message) An accompanying error message.
-
Constructor Details
-
ErrorInformation
public ErrorInformation()
-
-
Method Details
-
setCode
The error code:
- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- Parameters:
code
- The error code:- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- See Also:
-
getCode
The error code:
- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- Returns:
- The error code:
- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- See Also:
-
withCode
The error code:
- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- Parameters:
code
- The error code:- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
setCode
The error code:
- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- Parameters:
code
- The error code:- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- See Also:
-
withCode
The error code:
- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- Parameters:
code
- The error code:- APPLICATION_MISSING: The application was missing. This error code will most likely be raised if the application is deleted after the deployment is created but before it is started.
- DEPLOYMENT_GROUP_MISSING: The deployment group was missing. This error code will most likely be raised if the deployment group is deleted after the deployment is created but before it is started.
- HEALTH_CONSTRAINTS: The deployment failed on too many instances to be successfully deployed within the instance health constraints specified.
- HEALTH_CONSTRAINTS_INVALID: The revision cannot be successfully deployed within the instance health constraints specified.
- IAM_ROLE_MISSING: The service role cannot be accessed.
- IAM_ROLE_PERMISSIONS: The service role does not have the correct permissions.
- INTERNAL_ERROR: There was an internal error.
- NO_EC2_SUBSCRIPTION: The calling account is not subscribed to the Amazon EC2 service.
- NO_INSTANCES: No instance were specified, or no instance can be found.
- OVER_MAX_INSTANCES: The maximum number of instance was exceeded.
- THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more AWS services.
- TIMEOUT: The deployment has timed out.
- REVISION_MISSING: The revision ID was missing. This error code will most likely be raised if the revision is deleted after the deployment is created but before it is started.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
setMessage
An accompanying error message.
- Parameters:
message
- An accompanying error message.
-
getMessage
An accompanying error message.
- Returns:
- An accompanying error message.
-
withMessage
An accompanying error message.
- Parameters:
message
- An accompanying error message.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
toString
Returns a string representation of this object; useful for testing and debugging. -
equals
-
hashCode
public int hashCode() -
clone
-