- 最新
- 最多得票
- 最多評論
Hi,
Your ECS task definition (see https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ecs.TaskDefinition.html) points to a container image.
If you update your image, you must update the task definition in CDK so that it takes the latest image.
AWS recommendation is to not use 'latest' as image tag but commit id.
So, you CDK project should make use of an env var defining the commit id to use for the image tag included in the task definition
Best
Didier
This is fair (and I've avoided using 'latest' for just this reason), but I've avoided this because that would mean I'd need to deploy from specific machines or environments. Not just anyone could run cdk deploy on their machine. In the past I've tried dynamic aws api calls within CDK to grab dynamic bits of configuration (like the most recent task definition, for instance), but this has traditionally caused problems/frustration.
Thnak you for the feedback and acceptation of answer
相關內容
- 已提問 10 個月前
- 已提問 6 個月前
AWS 官方已更新 2 年前- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Hi, I would suggest to update your question with the ECS-relevant part of your CDK code. That would help to understand how you ask ECS to choose the container image.
Hi! I suspect this would actually not help much - my CDK based task definition has a "dummy" container image. It just deploys a vanilla image of nginx. When the github action runs, it creates a brand new task definition that pulls from an ECR repo. This is why my cdk service updates are a problem - it reverts to the dummy nginx image.