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

It is currently scoped to the backend you are logged in to. So if you store your stacks in different s3 buckets, you will only see ones in the same bucket.

this seems to be a problem when I create a stack on one machine and then try and work with it on another

`$ pulumi login --cloud-url <s3://dc-synchronicity-pulumi/synchronicity-idm>`

```$ pulumi stack ls
NAME  LAST UPDATE  RESOURCE COUNT
```

there definitely definitely is stack state in that bucket

```backend:
  url: <s3://dc-synchronicity-pulumi/synchronicity-idm>```

ah, no, it’s because `PULUMI_CONFIG_PASSPHRASE` was either wrong or not set - that seems to cause `pulumi stack ls` to fail silently