brave-motorcycle-6748711/22/2022, 7:47 PM
. In the apps' repos, I have Github Actions rules that build the containers and push them to ECR. Now I need to close the gap between these two. My thought was that I'd trigger CodeDeploy from Actions (we're doing that for the old process I'm replacing) and that would handle the deployment. The problem is that the next time I run
, it'll re-deploy some old version of the app. Ideally I'd just leave that field out, but it is required by the SDK. The few things I've found about how other people do this is to run pulumi in the deploy pipeline and pass it the container version in an environment variable. I don't particularly want to run all of the infrastructure configuration stuff on a code deploy, though (and especially don't want changes to infra to potentially roll out while a developer is running what they think is a normal code deploy). But is that what I have to do?
little-cartoon-1056911/22/2022, 9:30 PM
stacks in this project, you'll create a new version of the TaskDefinition, and ECS will handle deploying the image and draining old containers.
cycles: you'll deploy images to various ECS clusters much more frequently than you'll push images to ECR.
brave-motorcycle-6748711/22/2022, 9:42 PM
little-cartoon-1056911/22/2022, 10:28 PM
brave-motorcycle-6748711/22/2022, 10:40 PM
little-cartoon-1056911/22/2022, 10:44 PM
brave-motorcycle-6748711/22/2022, 10:46 PM
is an example, where it's referring to a tag but that tag can change to whatever.
little-cartoon-1056911/22/2022, 10:47 PM
brave-motorcycle-6748711/22/2022, 10:47 PM
little-cartoon-1056911/22/2022, 10:48 PM
brave-motorcycle-6748711/22/2022, 10:49 PM
little-cartoon-1056911/22/2022, 10:50 PM
brave-motorcycle-6748711/22/2022, 10:51 PM