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

It would do numbers for the organization of our configs

Yes - your `Pulumi.yaml` file can include a `main: ` which points to another folder that contains that `__main__.py`. 

See <https://www.pulumi.com/docs/intro/concepts/project/#pulumi-yaml>. 

This is great, is it possible for the configs to live in a subdir structure, such as `${root}/services/service1/service1.yaml`

image.png

In your `Pulumi.yaml` you can specify a different directory to load config files from.

Yep, that makes sense, but does it recursively look for them, is my question

Oh, I see. No, I believe we don't currently support that.

The idea would be so that you can store templates along with your stack files

Do you think people would be receptive to a change in this behavior?

Could you open an issue at <https://github.com/pulumi/pulumi> with your use case? Can discuss in that.

<https://github.com/pulumi/pulumi/issues/3476>