Hi everyone, I’m just getting started trying out Pulumi with some basic state. I have an S3 bucket and a EB Environment defined in a single

index.ts

file and I’m trying to refactor this into multiple files/directories. However, I’m getting inconsistent import behavior once I split these files into different directories.

pulumi preview

will sometime show 0 changes, sometimes it will try to delete my EB environment that’s a few layers of imports deep. I put log statements in my files and it looks like sometimes it doesn’t import the file it’s defined in. 1. Are there any articles/docs on refactoring pulumi programs I can read? 2. Do files need to have an export to be processed for pulumi state? My EB env is just declared as a

const

variable without exporting anything, and I’m wondering if that might be part of my issue. 3. Does pulumi cache my input program in any way?

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

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

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.