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

Should be able to. Another approach I like is editing the relevant `.js` file in the node_modules to add logging. Editing the JS files directly is a tighter feedback loop since you don’t have to recompile.

I tried `console.log` first, but nothing was displayed during `pulumi preview --diff`. Does Pulumi configure the NodeJS runtime with a different log sink?

And I do not need to edit anything in `node_modules`, as the ResourceTransformation is my own code within the Pulumi project

<@UE1LN7A22> So if I put `<http://pulumi.log.info|pulumi.log.info>` lines in my code, how can I make the output visible?

&gt; Does Pulumi configure the NodeJS runtime with a different log sink?
I don’t know for sure. I think I’ve used both in the past. The code gets run during preview, so I’d expect you to see any logging during preview and update

Found it. There was a bug in my code which result in my transformation not being set on the resource. So my transformation wasn’t invoked at all. :blush: