This message was deleted.

This indeed an open issue: https://github.com/pulumi/pulumi/issues/2522

Thank you! Meanwhile, I've found a workaround. The following seems to isolate projects for me:

PULUMI_BACKEND_URL=file:///tmp/1 pulumi stack ls

PULUMI_BACKEND_URL=file:///tmp/2 pulumi stack ls

@able-ability-11203 you’re better off prefixing your stacks with the project name

pulumi stack init <http://myApp.dev|myApp.dev>

pulumi stakc init <http://infrastructure.dev|infrastructure.dev>

Different backends (e.g. azure blob) will have issues with duplicate named stacks as they can be stored in a "flat" structure. I've employed a naming convention for "stack" names of

<project>.<stack>

so

<http://infrastructure.dev|infrastructure.dev>

,

infrastructure.prod

would be what I would use. Although you could isolate projects to different backends, if you'd like to consume stack outputs from one stack in another, you'll need to use the same backend for both.

Thank you! Could I probably suffix them as well

dev.infra
<http://dev.app|dev.app>
prod.infra
<http://prod.app|prod.app>

? To quickly tell envs from one another.

as long as they’re unique you can name them how you like 🙂

Sounds good, thanks for prompt reply!