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

So I split my pulumi files to make the separation more logical, it seems when I run `pulumi preview` it thinks I deleted all the resources ? I did change my tsconfig file to include the new file..Any other pointers ?

are you importing _and referencing_ those resources?

you can’t just import them. node.js will not execute the file unless you reference something from that file.

What is the import part ? the resources already exist..I just wanted to refactor the structure

Like, you’ve put them in different files right?

How does pulumi know about the second file?

Exactly so how do I ensure pulumi knows about it ?

Whatever is in `index.ts` will be executed.

I added all files in the tsconfig.json file

```
   "files": [
        "index.ts",
        "helm-config.ts",
        "config.ts",
        "util.ts"
    ]
```

Okay so how do I ensure that it executes further

I see..so to maintain the sequential flow it needs to flow through index.ts

So, Pulumi isn’t doing anything magic, it’s literally just executing a nodejs app that happens to register a bunch of resources.

Nodejs apps require an index.js or (in our case) an index.ts

Yup..I was under the impression it will combine all ts files and then figure out the dependencies and stuff

You will typically want to have an `index.ts` file that imports everything you want to include and exports everything you wants to expose.

If there are components that file wants to include but not otherwise reference, you can use `import "./something.ts"` to ensure they are imported.