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

Are you talking about a configuration value or just something you want to have present no matter which config is used? If it’s not a secret, why not putting it into the program that is used in several stacks?

Another way (if used over several projects) could be to extract that information into a (private) node module.

That was my thought <@ULXSQT866>. If it’s not something that changes, just have a constants file that you can reference in your project (and across all stacks)

Yeah that what i was thinking about. Thx. :slightly_smiling_face:

If it’s about some secrets that should be used in several stacks, there is always the option of creating a simple stack that just exports those values and using a static `StackReference` to import data from there (even if this is not really the main use case for stack references)

For the latter, check out this link: <https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/#inter-stack-dependencies>