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

Hey guys, so I was looking at pulumi/pulumi/runtime/config.js and I noticed that the config file that we create for each stack, is set into an env variable called ```PULUMI_CONFIG``` This means that when we do ```Pulumi Up``` the file is loaded as a string and parsed into a map. This would mean that if we wanted to have a hierarchical config structure for the config, we need to append the base config to this env_variable ```PULUMI_CONFIG``` .  My suggestion seems so hacky. As a team we decided to create a wrapper class for the config that reads from the pulumi Config class and also from a file. This way we can have a one level hierarchical structure.