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

Generally the best way to disable the ambient providers is to set fake values for its configuration - e.g. `pulumi config set azure:environment invalid`.

We have an issue at <https://github.com/pulumi/pulumi/issues/3383> to make this more explicit.

• `pulumi config set kubernetes:kubeconfig invalid`
This works, thanks! I like the fact that is is in pulumi.yaml and that I can commit that to git.

What about disabling azure.core.getClientConfig({}) in my pulumi code ?   (environment: invalid - doesn't allow that to go away)

To clarify - if pulumi needs to access that internally (e.g. to get credentials for executing 'up')  that's fine, I just want to reliably ban uses of that from the checked-in pulumi program.

I'm not sure if Pulumi requires that internally and don't know of a way to disable it.