This message was deleted.

sparse-intern-71089

02/10/2020, 9:56 PM

This message was deleted.

rhythmic-finland-36256

02/10/2020, 9:59 PM

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?

rhythmic-finland-36256

02/10/2020, 10:00 PM

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

handsome-actor-1155

02/10/2020, 10:00 PM

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

big-potato-91793

02/10/2020, 10:01 PM

Yeah that what i was thinking about. Thx. 🙂

rhythmic-finland-36256

02/10/2020, 10:02 PM

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)

rhythmic-finland-36256

02/10/2020, 10:03 PM

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

big-potato-91793

02/10/2020, 10:33 PM

nice thx 🙂

2 Views

Open in Slack

Previous Next

Pulumi Community

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.