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

<https://github.com/pulumi/pulumi/issues/2522>
Long standing issue we haven't got around to yet, I'm afraid.

Too bad, as it makes naming a total mess unless we create multiple blob storages for each project. Any idea when this will be fixed?

Is this issue a complicated one? Naively I would assume its enough to simply combine project_name+stack_name when writing and reading state?

I don't. I know most people either use multiple backends (i.e. make the project name part of the backend path) and set that in the Pulumi.yaml, or they just prefix all their stack names with the project name.

The complexity is mostly one of making sure we don't break everyone in the move to the new semantics.

Fair enough, we opted for the last one for now, but it makes naming kinda chaotic.

Hard to see how you would avoid breaking without separate paths, but I will follow this issue closely. Thank you :slightly_smiling_face: