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

Hi <@U01C549817F>

That isn't available yet but that work in planned for this quarter so we hope to deliver it soon:tm:

Is there anything wrong with my approach of doing a `pulumi login` to a different bucket for each stack? It seems like that does the job, and that `pulumi stack ls` will only show the stacks that have been saved to that bucket (in this case, it will be one stack per bucket)

Not at all - that’s the suggested way at that time 

Why would `pulumi stack ls` show me stacks that are not part of the current bucket? I’ve done `pulumi login <gs://my-state-bucket>` which is a brand new bucket, and when I do `pulumi stack ls` I can still see a bunch of stacks that are defined by a different bucket

Okay I figured it out: it was the `backend: url:` config in `Pulumi.yaml`