This message was deleted.

i quickly skimmed thru the github workflow yaml and overall approach - having spent a lot of time in the past few weeks on github actions and pulumi - the answer to your second question is yes

Great, thanks @many-yak-61188! It looks like a pretty sane approach. My best guess for why it isn’t officially endorsed or catered for with the CLI would just be that

pulumi

has a broader use-case than the serverless frameworks. Preview builds is an obvious approach for most projects that use

serverless

, Amplify, Netlify, Vercel etc, given it generally doesn’t cost you anything to spin up a fresh stack. I guess users of

pulumi

are more likely to have stacks that you couldn’t just create duplicates of at will and therefore using

pulumi preview

to check the changes is the next best thing (to creating a fresh isolated environment for each PR).