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 <@UV2JTHE9F>,

I would love to be able to say yes here but unfortunately we have no story for hierarchical config files (at this time). YOU COULD *potentially* split out any of your own application config and have your application read and parse that yaml but I don't suggest that when it comes to any provider specific config (e.g. aws:region, gcp:project) or secrets as it may not work as expected

I see. Thanks. I can still opt out to a step in pipeline to pull them from config repo and merge

I worried about this for a while, then as I migrated more infra into Pulumi, I found that I was getting rid of more and more config. Everything that started off as config later became stack references. You may find that you need far fewer config values than you think...