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

For ease of implementation and keeping all secondary files formatted the same, my thought is to start with Global referencing vs. relative.

<@U0595UV0A3D>   <@UCU9C7W73> created a great blog article to use various other languages to create a single YAML input for Pulumi YAML from various code files utilizing the compiler property of a Pulumi.yaml file. 
<https://www.pulumi.com/blog/extending-pulumi-languages-with-yaml-cue-jsonnet-rust/|https://www.pulumi.com/blog/extending-pulumi-languages-with-yaml-cue-jsonnet-rust/>

To combine various YAML fragments into one single YAML file, which can be used as input for Pulumi YAML, I'd go for yq <https://github.com/mikefarah/yq|https://github.com/mikefarah/yq>

I did read that article, but I hadn't thought about `yq` as a compile option, that's a cool idea.