I asked the other day about where your Pulumi code should live in relation to your code repo, and there seemed to be a lot of consensus around putting it in

/infra

(see conversation here). Now, I’m following a tutorial that covers using separate projects for building a Docker image and pushing it to my cloud provider of choice: https://www.pulumi.com/docs/tutorials/gcp/gcp-ts-docker-gcr-cloudrun/ In this case, would it make sense to have two separate Pulumi folders? (

/build

and

/deploy

or something like that) Or should I always be building and deploying in a single step? I’m coming at this with some experience using Docker and docker-compose, so I’m used to building, pushing to a registry, and then pulling the image as three separate steps.

Pulumi drives towards a desired state, so you should really be putting them in the same dir, it's a little different to the docker-compose style workflow

Thanks. I’m going to read up on this (I see it discussed here: https://www.pulumi.com/docs/intro/concepts/how-pulumi-works/).