@fierce-ram-50276 Yeah - packaging up into a Docker Repository, or doing a Packer build of an AMI, or however else you build your deployable artifacts can happen in a deployment pipeline entirely separate from Pulumi - and then the Pulumi program can refer to the repositories or AMIs that are being published by that pipeline. Alternatively you can have two separate stacks, both in Pulumi, one which builds and pushes an image, and the other which references that image in Service. And then deployments of each can be triggered from the separate versioning contexts (perhaps pushes to two different repos).