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

You can split out the "common" parts into another project / stack and then reference that from the dependent stacks

<https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/#inter-stack-dependencies>

e.g `
```const common = new pulumi.StackReference(`acmecorp/common/shared`);```

pulumi doesnt have a concept of a hierarchical configuration model with overrides at arbitrary levels (correct me, please, if I'm wrong)

You can copy config from one stack to the other (new)
<https://github.com/pulumi/pulumi/issues/1583>

<@URABGC3T7> that's a smart one. Thanks much

I would like to suggest dev team to consider using the `Pulumi.yaml` as global shared config between stacks. Thoughts?