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

guess stacks need to be in same project :S <https://github.com/pulumi/pulumi/issues/3395>

The main problem is that we can't use multiple backends, e.g., both the Pulumi service and S3. Is that your case too?

I just had different projects in different storage paths, e.g. <azblob://pulumi/projecta> and <azblob://pulumi/projectb> ... but couldn't get that wroking

I've just used my own naming convention on top of stack names. So a stack name wouldn't be simply `dev` or `stg`, but `project-name.dev`, `project-name.stg`, etc. And I store them all in a single Azure storage container. This affords me cross-project stack references.

Something along those lines is described in this blog post: <https://blog.scottlogic.com/2020/04/21/starting-with-pulumi.html>

You can create an azure key vault as part of the pulumi program and store the values in there. Then in other stacks you can azure.keyvault.getSecret()

if you go this route, be sure to grant your current identity read/update/delete access policies to retain control of the key vault :slightly_smiling_face:

I went with one project with multiple stacks .. seems to work okay so far

That's fine. You'll have to split into multiple projects just when/if you need to deploy parts of your code separately. With a single project it's all or nothing — all infra code is executed.

yeah I'm looking to bring more devops people into this, so would prefer to have things properly split up instead of all or nothing. Some of these things are also quite unrealted