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

sure, you just just `pulumi login` to the apropos place before interacting with the stack.  it definitely adds some management overhead to make the right decisions etc.

I do this with s3 backends all the time - stacks live on different accounts with their own s3 bucket, so there's a login involved in every stack switch

i was hoping I could skip that login step somehow

not in the current world.  (I built a wrapper for my env to handle that automatically, it consumes it from the stack.yaml.  it also enforces that -s is always passed)

mind sharing that wrapper? :slightly_smiling_face:

the functionality to specify the backend config in Pulumi,yaml was recently added

I wonder if it would be possible to extend it to stack configs

<@UKA1VMF5Z> got a link to that?  I haven't seen it (and it didn't come up on the various issue/pr threads I've been involved with around this)

sure, <https://github.com/pulumi/pulumi/pull/2813>