No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Screenshot 2022-03-28 at 19.36.17.png

Hey!
I’m having trouble with creating two pulumi projects. One has a stack “general” and the other has a stack “staging”. Running `pulumi stack ls`  shows both stacks when I thought it should only show the stacks from the current project by default. The -p option does not change anything. Using `pulumi stack select theoneintheotherdirectory` creates a new yaml file…
Is that expected?

I’m using a GCS bucket to store the state, it seems to be the cause, it works better with the pulumi service backend

yes, you need to prefix the stacks like `{project}.{stack}`

there's no logical separation in the oss backends, because they're all in the same bucket