Request Syntax Request Parameters Response Elements Errors Examples See Also

ContinueDeployment

For a blue/green deployment, starts the process of rerouting traffic from instances in the original environment to instances in the replacement environment without waiting for a specified wait time to elapse. (Traffic rerouting, which is achieved by registering instances in the replacement environment with the load balancer, can start as soon as all instances have a status of Ready.)

Request Syntax


{
   "deploymentId": "string",
   "deploymentWaitType": "string"
}

Request Parameters

For information about the parameters that are common to all actions, see Common Parameters.

The request accepts the following data in JSON format.

deploymentId

The unique ID of a blue/green deployment for which you want to start rerouting traffic to the replacement environment.

Type: String

Required: No

deploymentWaitType

The status of the deployment's waiting period. READY_WAIT indicates that the deployment is ready to start shifting traffic. TERMINATION_WAIT indicates that the traffic is shifted, but the original target is not terminated.

Type: String

Valid Values: READY_WAIT | TERMINATION_WAIT

Required: No

Response Elements

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

Errors

For information about the errors that are common to all actions, see Common Errors.

DeploymentAlreadyCompletedException

The deployment is already complete.

HTTP Status Code: 400

DeploymentDoesNotExistException

The deployment with the user or AWS account does not exist.

HTTP Status Code: 400

DeploymentIdRequiredException

At least one deployment ID must be specified.

HTTP Status Code: 400

DeploymentIsNotInReadyStateException

The deployment does not have a status of Ready and can't continue yet.

HTTP Status Code: 400

InvalidDeploymentIdException

At least one of the deployment IDs was specified in an invalid format.

HTTP Status Code: 400

InvalidDeploymentStatusException

The specified deployment status doesn't exist or cannot be determined.

HTTP Status Code: 400

InvalidDeploymentWaitTypeException

The wait type is invalid.

HTTP Status Code: 400

UnsupportedActionForDeploymentTypeException

A call was submitted that is not supported for the specified deployment type.

HTTP Status Code: 400

Examples

Example

This example illustrates one usage of ContinueDeployment.

Sample Request


POST / HTTP/1.1
Host: codedeploy.us-east-1.amazonaws.com
Accept-Encoding: identity
Content-Length: 31
X-Amz-Target: CodeDeploy_20141006.ContinueDeployment
X-Amz-Date: 20170412T195720Z
User-Agent: aws-cli/1.11.76 Python/2.7.9 Windows/8 botocore/1.5.39
Content-Type: application/x-amz-json-1.1
Authorization: AWS4-HMAC-SHA256 Credential=AKIAIOSFODNN7EXAMPLE/20160707/us-east-1/codedeploy/aws4_request, 
	SignedHeaders=content-type;host;user-agent;x-amz-date;x-amz-target, Signature=39c3b3042cd2aEXAMPLE
	
{"deploymentId": "d-7S8EXAMPL"}