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

I’m going to try specifying the backend in the Pulumi.yaml file for each project and see if that works the way I’d expect.

You have two choices: you can specify different S3 backends via the `backend: url:` property (they can be different keys in the same bucket), or discriminiate stacks with projects names.

If you use different backends, you cannot access outputs of either stack from the other.

If you use the same backend then you have one bag of stacks. So you need your stacks to describe which project they belong to, in order to avoid confusion.

Only the Pulumi backend has built-in support for "this stack belongs to that project".

Also, it's the only one that supports organizations.

the general pattern is that people will prefix their stacks with a project name, like `infrastructure.dev`

Ok, thanks for the explanation. I definitely want to access the infrastructure outputs in the application stacks, so I guess I’ll need to use the naming conventions suggestion.

<https://github.com/pulumi/pulumi/issues/2522>