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.
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.
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events