This message was deleted.

I'm not sure if there is a written Pulumi guide for that, but we organize all of our resources into separate files, as necessary. Our

index.ts

files are kept VERY simple. They only import said files in the desired order. For example:

What do you export usually? ComponentResources, CustomResources, and/or (Dynamic) Providers?

It typically depends on if we need that resource in another file. If we do, we

export

it. Providers for sure. We define that provider in it's own file and

export

it, then reference it in all of the files that require a Provider.

There are many docs on how to organize projects! E.g. https://www.pulumi.com/docs/using-pulumi/organizing-projects-stacks/#organizing-your-project-code https://www.pulumi.com/docs/concepts/resources/components/#component-resources https://www.pulumi.com/blog/iac-recommended-practices-structuring-pulumi-projects/ https://www.pulumi.com/learn/abstraction-encapsulation/ https://leebriggs.co.uk/blog/2023/08/17/structuring-iac

in some situations where we have many sets of resources following the same pattern (conforming to the same interface(s)), we’ve resorted to this type of construction in index.ts:

Promise.all(
  fs
    .readdirSync(__dirname + '/resources')
    .map(file => import(__dirname + '/resources/' + file))
).then(resource => {
// declaring further dependent resources here
}