(Kubernetes) is there a best practice for creating a hierarchical config structure for the application. For example a base configurations that has app name, memory, cpu, & then consume the Pulumi.prod.yaml. Seems like pulumi is able to understand the stack and look to a specific file. Can there be a tree of config files that it consumes.

Pulumi.base.yaml -> Pulumi.prod.yaml  &&  Pulumi.base.yaml -> Pulumi.stage.yaml

@thankful-optician-22583 this was the core idea behind ksonnet, a hierarchy of env-specific config. We don’t have anything like this currently.

@creamy-potato-29402 thanks for your reply 🙂