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, How are you modularizing your pulumi code?

In general, I end up having multiple .ts files, where I have usually one main function that is imported and called from index.ts.

Example:

# index.ts

import { setupPermissions } from './permissions.ts'

setupPermisions(parameterA, parameterB)

# permissions.ts

export func setupPermisions(a, b) {
    pulumi resources...
}

maybe instead of this should I do a component resource in each module? :thinking_face:

There's any number of ways to do it, and they all have their advantages.
I always use ComponentResources as it gives me very definite boundaries for unit testing (everything in a ComponentResource) and where I can use elements like `pulumi.runtime` and `pulumi.Config` (index.ts only).

yes this is what I am realizing that might feel more natural or "the pulumi way"