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

apologies if this has been asked before but - does pulumi support a concept of a “base” <https://www.pulumi.com/docs/intro/concepts/config/|stack configuration file>, scoped in a particular project? eg:
• `Pulumi.&lt;base&gt;.yaml` - has the defaults
• `Pulumi.&lt;a&gt;.yaml` - has the `a` stack’s configs, as overrides from what is specified in `base`
• `Pulumi.&lt;b&gt;.yaml` - has the `b` stack’s configs … etc.

No. You can vote for it here: <https://github.com/pulumi/pulumi/issues/2307>

Two common workarounds:
1. Dave a project with a single stack, for the common config. Access the common config via stack references.
2. Do it using ordinary config support in your preferred language.

While Pulumi config is handy, it's not special in any way: you may prefer to use a different way of getting app configuration values from config files. It's fine to do that.