This message was deleted.

You can do. There's also good support for unit testing (on faked resources) and integration testing (on ephemeral resources), which can lighten the load.

For us, we have 3 git branches that correspond to 3 stacks: develop, staging, master. develop is always a brand new stack that brings things up and then destroys it all. We use testinfra for integration testing. The staging branch deploys to our nonprod environments and master to our production environments. Pulumi is extremely flexible in this regard so you can create whatever stacks you want to test out new code before deploying your production stack.

Thanks for the replies! How do you go about local development more specifically, I don't imagine you push on every change?

I run the tests every time, and push to git. My CI runs

pulumi preview

on every push that has an open PR, and fail the build if I don't like the return code. I run

pulumi up

manually when appropriate.

Gotcha thanks!