Hi all, looking for some advice on structuring Pulumi projects using YAML. We’re building a tool that generates Pulumi YAML programs for internal infrastructure-as-code use. As the number of resources grows (some very large), we’d like to support multi-file declarations — i.e., define different resource types in separate YAML files for clarity and maintainability. So far I’ve explored: • Merging multiple YAMLs into a single

Pulumi.yaml

before

pulumi up

• A multi-stack approach using

StackReference

for coordination • Generating a Python program dynamically from YAMLs, which offers flexibility but adds complexity Before going too far, I’d love to hear from the Pulumi team or community: → Is there a “native” or recommended way to do multi-file YAML declarations? → Any prior art or patterns you’ve seen for this? Thanks in advance!

We've been thinking about supporting multi-file as part of the runtime, just squash all the yaml files in the folder together rather than just reading the main one. Issue tracking that at https://github.com/pulumi/pulumi-yaml/issues/227 do vote if it would be useful.

Oh I see. We'd find this really handy for large resource declarations we are handling, so I left my vote. Thank you!