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

Hi. I am new to Pulumi and I was wondering what was the proper way to organize its code. Right now all my azure ressources are created in the Main of my Program.cs file which is getting bigger and bigger :disappointed:. Samples that I saw were doing the same thing which seems fine for a few ressources but as my infrastructure is growing it's getting less nice. Are there good practices to organize the code ?

If you have multiple resources that are related and produce a logical higher-level component, you can wrap them as Component Resources, e.g. like here <https://github.com/pulumi/examples/blob/master/azure-cs-cosmosapp-component/ArchiveFunctionApp.cs#L10>

If not, you are free to choose the structure based on classes/methods calling each other as you see fit

On a higher level, if you want to start deploying some of those resources separately, you may want to split them into multiple projects