Can the ambient configuration be disabled? I'm th...
# kubernetes
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: 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: you can specify a specific context for each
👍 1
Didn’t know there was an ambient context for kubernetes
I’ve been manually adding a provider
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