Does anyone have recommendations on how to think about the boundaries between Pulumi Deployments (enabled via UI + GitHub integration) and general Pulumi CI/CD? It seems like deployments enables running

pulumi up

on every commit that happens on a branch, say, the

main

branch. This would mean that only after you merge a PR does

pulumi

run. What do people do to preview changes during the branch development?

When you open a PR against the main branch a PR should run and comment on the PR automatically.

Will it just run

preview

on the PR and then once it merges it runs

up

?

yep!

oh sweet!

And for local development during the branch

There are a couple of options here: 1. you can create a new branch and a new stack, and then set deployment settings on that branch, including OIDC, etc. That way a developer can just push commits to a branch and the stack automatically gets updated in the background. 2. you can create a new branch and stack, and then have the developer run

pulumi up

locally, but this requires giving them cloud credentials on their local machine Both are great workflows.

cool, cool, thank you!