This message was deleted.

sparse-intern-71089

05/15/2022, 2:19 PM

This message was deleted.

few-yacht-11623

05/15/2022, 2:39 PM

nevermind, it sounds like I am just hitting generic typescript/ecmascript issues with module loading. I must not understand the behavior when importing modules with no exports. I was using

export * from './subtree'

and I swapped those to

import './subtree'

and now it is working consistently

few-yacht-11623

05/15/2022, 2:41 PM

still any resources on factoring / organizing pulumi state would be helpful!

sparse-park-68967

05/16/2022, 1:29 PM

I assume you are asking about how to organize stacks? Some approaches are mentioned here: https://www.pulumi.com/docs/guides/organizing-projects-stacks/

few-yacht-11623

05/16/2022, 6:24 PM

I’m more interested in how to organize files within a single stack, really. Do most people just do one TS file per stack?

few-yacht-11623

05/16/2022, 6:28 PM

all of the examples on that page seem to show a single

.ts

file per stack

few-yacht-11623

05/16/2022, 6:28 PM

but I am imagining people would use shared TS utilities, and separate infrastructure into multiple files in a given stack. And that is the part I’m curious about

sparse-park-68967

05/16/2022, 6:38 PM

You have the freedom to organize the code the way you prefer and bring your code style over - lots of examples in Pulumi/examples repo use multiple files. For simple things single file is sufficient but for more complex environments I have seen lots of namespaces etc.

4 Views

Open in Slack

Previous Next

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.