https://pulumi.com
Join Slack
This message was deleted.
# typescript
s
This message was deleted.
f
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:
🙌 1
With that said, of course that means that we 
export
resources all over the place 😆
s
What do you export usually? ComponentResources, CustomResources, and/or (Dynamic) Providers?
f
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.
We do the same thing for ComponentResources, but don't really use CustomResources
👍 1
l
a
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:
Copy code
Promise.all(
  fs
    .readdirSync(__dirname + '/resources')
    .map(file => import(__dirname + '/resources/' + file))
).then(resource => {
// declaring further dependent resources here
}
🙌 1
2 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by