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

Why would projects share stack configs?

You can use Global project config per project, btw.

`Pulumi.yaml` can have configuration that the stacks inherit.

So rather than re-specifying the same data structures in my yaml every time, I'd like to be able to define it once and just have them read that.

Common values like environment layout, regions, etc...

You might be desired a "shared project" with stack outputs and references pattern

e.g.

`shared-projectname-infrastructure` standing up things like an ALB and secrets, parameters. Then you output their IDs, and use StackReferences in the "child" stacks to get the values.

<https://www.pulumi.com/blog/iac-recommended-practices-using-stack-references/>

Could see that working.  A little convoluted, but it lets me specify things once and then I get strongly typed references going forward.  Thanks :slightly_smiling_face: