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

Can the ambient configuration be disabled?

I'm thinking, perhaps I can turn `pulumi config set kubernetes:context my-context` into a required variable(?)

re: <https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/setup/#kubernetes-configuration>

My goal is to avoid running pulumi against the wrong cluster (I need to switch between two live clusters often...)

Is there perhaps another defensible way to configure pulumi?

the way to handle this is to set a provider resource on your Kubernetes resources:
<https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/>

you can specify a specific context for each <https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/#context_nodejs>

Didn’t know there was an ambient context for kubernetes

Although, I like that approach because I can just swap providers out from rendering to yaml to deploying

Kinda in this vein, is there a way to disable persistence of config? I’d like to force certain values to be provided at the CLI every time