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

hey, I have a hard time wrapping my head around stack naming. so for some reason, I see examples with `acmecorp/app/env` but my stacks cannot be named with a `/` I am using pulumi without the service, just at a s3 location. how can i structure my stacks in a good way&gt;

to add to this: when I create the stack `dev` in my project `dummy` , it is saved in my s3 bucket as `dev.json` preventing any more dev stacks in any projects.

this is a limitation of the way we do these backends, the suggestions it to call your stack `&lt;projectname&gt;-&lt;stack&gt;` when you login