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 😉
Thanks
Is it fine to replace Fargate task-defination like this? .. AWS specification says that we need to create new task definition. 🤔 ... But sure I will give it a try 😊
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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'
IMAGE_NAME: nginx
Soon we will update the documentation and schema to officially support this, thanks you for the report!
Regards, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Halyna Berezovska But, it won't work because, in script, the image parameter in `update_task_definition` method, is not getting updated. `image` parameter is just getting passed to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ashwani Kumar yes, I see... Looks like this is a bug or not supported feature. Thanks for reporting, I will let you know once that is enrolled fully
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a workaround for now I can see you could put tag right to the definition like you do and before you can remember this tag as a variable if it is possible. Or you could parse definition json file with jq and get the tag.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Halyna Berezovska , 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 .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.