This message was deleted.

One blocker I've got is that I'm using the deployment instance stack name as a source of uniqueness in my resource names

Why are you not relying on pulumi to autoname things?

which of course doesn't exist unless the pulumi runasync() is called

Can't you use mock stacks for this?

Are you running unit tests (with "mock" stacks) first, before your real-stack integration tests? I prefer the unit-style tests within Pulumi, and then integration-style tests outside Pulumi (using the normal SDKs of the cloud).

Not yet - but that seems very appealing... I need to look that up - are there examples you could point me at (I don't care which language, I'll adapt/look). Thank you!