Class ErrorInformation

    • Method Detail

      • code

        public final ErrorCode code()

        For more information, see Error Codes for CodeDeploy in the CodeDeploy User Guide.

        The error code:

        • APPLICATION_MISSING: The application was missing. This error code is most likely 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 is most likely 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 Amazon EC2.

        • NO_INSTANCES: No instances were specified, or no instances can be found.

        • OVER_MAX_INSTANCES: The maximum number of instances was exceeded.

        • THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more Amazon Web Services services.

        • TIMEOUT: The deployment has timed out.

        • REVISION_MISSING: The revision ID was missing. This error code is most likely raised if the revision is deleted after the deployment is created, but before it is started.

        If the service returns an enum value that is not available in the current SDK version, code will return ErrorCode.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available from codeAsString().

        Returns:
        For more information, see Error Codes for CodeDeploy in the CodeDeploy User Guide.

        The error code:

        • APPLICATION_MISSING: The application was missing. This error code is most likely 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 is most likely 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 Amazon EC2.

        • NO_INSTANCES: No instances were specified, or no instances can be found.

        • OVER_MAX_INSTANCES: The maximum number of instances was exceeded.

        • THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more Amazon Web Services services.

        • TIMEOUT: The deployment has timed out.

        • REVISION_MISSING: The revision ID was missing. This error code is most likely raised if the revision is deleted after the deployment is created, but before it is started.

        See Also:
        ErrorCode
      • codeAsString

        public final String codeAsString()

        For more information, see Error Codes for CodeDeploy in the CodeDeploy User Guide.

        The error code:

        • APPLICATION_MISSING: The application was missing. This error code is most likely 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 is most likely 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 Amazon EC2.

        • NO_INSTANCES: No instances were specified, or no instances can be found.

        • OVER_MAX_INSTANCES: The maximum number of instances was exceeded.

        • THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more Amazon Web Services services.

        • TIMEOUT: The deployment has timed out.

        • REVISION_MISSING: The revision ID was missing. This error code is most likely raised if the revision is deleted after the deployment is created, but before it is started.

        If the service returns an enum value that is not available in the current SDK version, code will return ErrorCode.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available from codeAsString().

        Returns:
        For more information, see Error Codes for CodeDeploy in the CodeDeploy User Guide.

        The error code:

        • APPLICATION_MISSING: The application was missing. This error code is most likely 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 is most likely 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 Amazon EC2.

        • NO_INSTANCES: No instances were specified, or no instances can be found.

        • OVER_MAX_INSTANCES: The maximum number of instances was exceeded.

        • THROTTLED: The operation was throttled because the calling account exceeded the throttling limits of one or more Amazon Web Services services.

        • TIMEOUT: The deployment has timed out.

        • REVISION_MISSING: The revision ID was missing. This error code is most likely raised if the revision is deleted after the deployment is created, but before it is started.

        See Also:
        ErrorCode
      • message

        public final String message()

        An accompanying error message.

        Returns:
        An accompanying error message.
      • hashCode

        public final int hashCode()
        Overrides:
        hashCode in class Object
      • equals

        public final boolean equals​(Object obj)
        Overrides:
        equals in class Object
      • toString

        public final String toString()
        Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be redacted from this string using a placeholder value.
        Overrides:
        toString in class Object
      • getValueForField

        public final <T> Optional<T> getValueForField​(String fieldName,
                                                      Class<T> clazz)