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

It's not in my path, do I need to add it? All of the pulumi work I'm doing is in NodeJs

yes you still need the pulumi CLI in your path as that’s where the engine is invoked from

I am testing pulumi in our app that is deployed on a kubernetes cluster, so I don't believe the CLI on my machine is relevant here. Let me know

the CLI needs to be wherever you invoke Pulumi from

Ok, so what should I do when I have it configured

it should just work. If you’re putting your Pulumi App on a Kubernetes cluster, you’ll just need to ensure it exists on your path in your docker container

<https://github.com/pulumi/automation-api-examples/tree/main/nodejs/inlineProgram-ts> This documentation says that the Pulumi CLI installation is needed but then says "No invocation through the Pulumi CLI required". Pulumi is working in other areas of our application and we are not invoking the CLI

“No invocation through the Pulumi cli is required” means that you don’t drive the application through the cli, run Pulumi up. That’s done for you with automation api

You need the cli to be installed and in your path for automation api to work 