Hi, I am able to create and push docker image on ECR with Bitbucket pipeline. And, now I want to deploy my container using the pipe - AWS ECS deploy - provided by Bitbucket. But I think there should be an option to pass the tag name. Because it would help me in the rollback, in case of wrong deployment. Currently I can only specify tag in the ECS's container definition only.
I looked at your pipe's code and found out that you are already trying to retrieve the IMAGE_NAME, but it is not mentioned in example. It would be great if you can enable that 😉
@Ashwani Kumar Yes, you are right, it is not explicitly supported.
Actually, you can try to deploy with IMAGE_NAME variable (like "python:3.7-slim" or something). You could have your pipe definition as:
script: - pipe: atlassian/aws-ecs-deploy:1.1.4 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: 'us-east-1' CLUSTER_NAME: 'your-ecs-cluster' SERVICE_NAME: 'your-ecs-service' TASK_DEFINITION: 'task-definition.json'
Soon we will update the documentation and schema to officially support this, thanks you for the report!
Thanks @Galyna Zholtkevych , I was thinking on the same page and changed the tag in AWS task definition JSON, which I copied from my Fargate configuration. But, I am having errors "Unknown parameter in input:", So currently I am trying to solve them. 🙂
If this works, then I will have fully automated CI/CD .
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
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