No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Generally, the image would be pushed to the repo by a workflow / pipeline in the app / Dockerfile repo, wouldn't it?

Else you run the risk of building a new image every time you do a deployment. Which isn't generally the right thing to do. You want to deploy a previously-released and accepted image.

That is true, I will stick with that. I was just following the official Pulumi examples which couple them (e.g. <https://github.com/pulumi/examples/blob/master/aws-ts-hello-fargate/index.ts> and others) so thought there might be a convenient way to approach it. Thanks tenwit!