On the new pipelines ecs script can you add an option for force deploy. Thanks.
Hi @[deleted]. Thanks for suggesting that. Can you please describe your use case so we can better understand the requirement and improve the pipe. In particular, we'd like to know why you need to do a forced deploy. As of now the aws-ecs-deploy pipe creates a new task definition every time, so it seems like the forced deployment isn't required.
Hi,
The way we are doing our deployment is that we have a task definition set for our production which uses an image in AWS ECR. When we have a new build we update that same image and then we need to deploy it to the same task definition. Looking at the ECS api the only way to have same task definition pull the image again is to use force deploy. This can be done via the console or the cli which we are doing in our pipelines now (aws ecs update-service --cluster $AWS_ECS_CLUSTER --service $AWS_ECS_SERVICE --force-new-deployment). ECS will then take each instance of task and update with new images. I hope that makes sense.
Arash
Hi @Alexander Zhukov ,
Is this possible on current version of Bitbucket Pipeline script?
If possible then how?
Regards,
Hiromi.
Hi @Hiromi , currently, the pipe registers a new task definition every time you run in, so the new deployment is always triggered and the new image will be pulled.
It looks like you're new here. Sign in or register to get started.
