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

Why do fully qualified stack names not include the project name?

On the website it's `{org-name}/{project-name}/{stack-name}` in the UI and URLs.
On the CLI it's `{org-name}/{stack-name}`.

This gets confusing when you have two projects in the same org with the same `{stack-name}`.

I reserve the right to "not get it" too :slightly_smiling_face:

I believe there is an open issue about this :smile:

Cool, I'll give it a :thumbsup: . (Couldn't find it either)

Where specifically are you seeing it be `org-name/stack-name`?

There is an issue that the local backend still uses `org-name/stack-name`, but everything in the CLI that works with the <http://pulumi.com|pulumi.com> backend should be including project name.

When you are in the context of a project (in a folder with a Pulumi.yaml), many CLI verbs will allow specifying things without project-name being explicit.

See <https://github.com/pulumi/pulumi/issues/2522> for the local backend issue here.

image.png

&gt; (in a folder with a Pulumi.yaml), many CLI verbs will allow specifying things without project-name being explicit.

Is the org name required then too?

At this time, I'm confident to say that I'd prefer to see the explicit name here `LykkeCorp/sample-react-app/sandbox`

For whatever reason, it make me a bit uncomfortable "Am I pointing at the right sandbox stack"

Would you mind opening an issue at <https://github.com/pulumi/pulumi/issues/new> to track the suggestion to be more explicit here - and the reasons you want that?  I do agree that these should most likely be explicit even when in a project context.

Thanks for the validation <@UB3BGTV63>; will do that.