This message was deleted.

@average-receptionist-65239 hard to say for sure, but usually this is usually a problem with the way JS/TS imports work. if you import but don’t use anything from a file then any resource definitions in there don’t get used.

Hm, okay. I put that import back, of course. I continued work by adding another resource in a separate module and importing it into my

index.ts

file. I had a similar experience where the Pulumi wants to delete 7 resources. If I place the new resource in one of my existing modules, then it works fine!

sorry, just to be clear—you have to import and also reference something from that file. otherwise the file does not get evaluated.

Yes, I understood you but I checked some of my existing modules and I don't export anything from them. I just expected them to get evaluated for their side effects (i.e.

new

some k8s resource). Quite a few of my existing modules to do not export anything. My index.ts looks something like:

import * as pulumi from "@pulumi/pulumi";

export * from "./namespace";
export * from "./credentials"
export * from "./tls";
export * from "./serviceA";
export * from "./serviceB";
export * from "./cronJobA;
export * from "./cronJobB";

Occasionally, I do export from those resource modules for debugging/learning purposes. Something like:

export const serviceaURN = serviceA.urn;

As I have gotten comfortable with Pulumi, I've been removing these exported constants.

@average-receptionist-65239 if you do figure it out I’d love to know what happened. I only ran into this once when I worked at pulumi and it drove me crazy for a few hours. 🙂

Switching to

import "./serviceA"

for all modules that do not export anything works. This is the official TypeScript way to import for side-effects, AFAICS. The strange part is why, up to this point, the

export * from "./serviceA"

was working. I'll see if I can work up a small repro over the weekend.

oh that makes sense.