blue-green-deployment | Blue-Green Deployment scripts | Continuous Deployment library

From the question it is not clear why you would require two provider definitions. But for the sake of example we can consider the below common use cases for blue/green deployment:

• target different clusters
• target different contexts

In both cases it will be easier to use a single provider with different provider configuration based on the flag set in variable.

Considering a variable definition like (using a string type but a bool can also be used):

"The AppSpec file for an Amazon ECS deployment specifies your task definition, container name, and container port."

Please refer to this article for more information - https://docs.aws.amazon.com/codedeploy/latest/userguide/tutorial-ecs-create-appspec-file.html

You didn't mention which error you get when you invoke the pipeline? Are you getting this error:

"The deployment failed because no instances were found in your green fleet"

Taking this assumption, since you are using manual tagging in your CodeDeploy configuration, this is not going to work to deploy using Blue/Green with manual tags as CodeDeploy expects to see a tagSet to find the "Green" instances and there is no way to provide this information via CodePipeline.

To workaround this, please use the 'Copy AutoScaling' option for implementing Blue/Green deployments in CodeDeploy using CodePipeline. See Step 10 here [1]

Another workaround is that you can create lambda function that is invoked as an action in your CodePipeline. This lambda function can be used to trigger the CodeDeploy deployment where you specify the target-instances with the value of the green AutoScalingGroup. You will then need to make describe calls at frequent intervals to the CodeDeploy API to get the status of the deployment. Once the deployment has completed, your lambda function will need to signal back to the CodePipeline based on the status of the deployment.

Here is an example which walks through how to invoke an AWS lambda function in a pipeline in CodePipeline [2].

Ref:

[1] https://docs.aws.amazon.com/codedeploy/latest/userguide/applications-create-blue-green.html

[2] https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-invoke-lambda-function.html

Your task definition is not valid. From a quick look I can see following invalid property:

No existing requests will be terminated or impacted in any way. The article itself talks about how you gradually move traffic from one blue to green. It doesn't abruptly terminate the requests.

I think this part gives some confusion:

we swap blue with green

The swapping is not a destructive operation where you kill one instance and start using another one. The swapping is just telling traffic manager to point to another IP. Requests pointing to the old IP are not impacted.

You can test this by creating an endpoint that holds a connection for a long time. Then while connection is held, click swap. Have logging to see what happened.

For App Service specifically, the documentation says this:

The traffic redirection is seamless, and no requests are dropped because of swap operations.

https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots