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

<@U03G8SBSJ58> absolutely, check out: <https://www.pulumi.com/docs/guides/organizing-projects-stacks/>. If you are worried about access control as well to those projects and stacks you should check out the following features in the pulumi service: <https://www.pulumi.com/docs/intro/pulumi-service/teams/>
&amp; <https://www.pulumi.com/docs/intro/pulumi-service/projects-and-stacks/#stack-permissions>

Hey, thanks for the reply, I've looked at <https://www.pulumi.com/docs/guides/organizing-projects-stacks> but I'm not sure exactly how I would implement any other config file pattern than what's mentioned there

All the examples mention `Pulumi.&lt;stack&gt;.yaml`  at the top level of the repo and the tools always create the stack config files in that location too

(Also `pulumi stack init`  always creates a file with that naming convention)

Aha. There is a StackConfigDir parameter :slightly_smiling_face: <https://www.pulumi.com/docs/reference/pulumi-yaml/>

Only took me reading the code to figure that out :sweat_smile:

Sorry about that I will talk internally about how to reference that in the organizing-projects-stacks doc