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

if you have projects on the same backed, then you should create the stack names fully qualified something like project.stac (app.dev)
if you have one backend per project, then you can't import stack outputs from one to another.

Those are mi insights.

My practice is to use the local backend for stacks not requiring collaboration (dev) and the pulumi app backend for stacks requiring collaboration (staging, CI, production).

+1 on fully-qualified stack names

<@U01400Z5N9Z>, do you mean fully qualified project.stack (e.g. myproject.dev)

or do you mean embed the stack name in the project?

<@U018MB4EBM3>, how do you manage the switching between the local and app backends?
You have to do a pulumi login each time, yes?

I guess I could set this up in an npm script

So far that happens infrequently enough that I've been manually logging in and out, but if that became burdensome I'd add login/logout to the repo `Makefile`  where we have commands like `make up PROJECT=foo ENV=prod`  -- as prefix and suffix to those commands.

It's possible that we'll move the dev stacks to the pulumi backend (in individual non-shared dev organizations) to avoid having to log out :slightly_smiling_face: