This message was deleted.

sparse-intern-71089

01/29/2020, 11:24 AM

This message was deleted.

white-balloon-205

01/29/2020, 3:15 PM

Could you share a little more (either here or in the issue) on what problem exactly you are trying to solve? There may be recommendations on alternative food approaches you can take today.

silly-dusk-21491

01/29/2020, 3:43 PM

We would like to define default values in a main configuration file then each environment configuration file would override only the necessary config values. Main point would be not to define redundant values in each environment.

white-balloon-205

01/29/2020, 4:52 PM

The typical way to do that today is to put default values in the Pulumi program. Does that work for your scenario?

silly-dusk-21491

01/29/2020, 5:28 PM

Yes, thanks that will work! I guess to get it from a config file we need to build some yaml merge script to combine default values and environment values.

white-balloon-205

01/29/2020, 5:30 PM

Great. Yes - if you want the defaults to live in YAML/JSON - you can read off disk - or else just put the default values directly in data in your

.ts

.py

files. The fact that it’s all just code means you can generally solve for hierarchicical config in very flexible ways without the need for a built-in feature.

silly-dusk-21491

01/29/2020, 5:57 PM

Yeah! That is the reason why I prefer Pulumi over Terraform!

🙂 1

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.