Kubernetes module triggers without env vars #5978
Labels
🐛 bug
Something isn't working as expected.
✅ existing workaround
When there is an unofficial way to solve an issue and there is no fix in starship yet.
Bug Report
Current Behavior
The kubernetes module is triggering with this configuration although there is no .k8s file in the current directory:
Upon investigation, this might be caused by the recent addition of detect env vars with #4488
Configuring
detect_env_vars
, e.g. withrestores the correct behavior (the module is not triggering if there is no file and the env variable is not defined)
Expected Behavior
Not defining the detect_env_vars option should not trigger the module.
Possible Solution
I imagine the env var detection done here https://github.com/andytom/starship/blob/4b1cda66417cec0ff146dadf8c673ef7198e919a/src/modules/kubernetes.rs#L110 either is faulty or should only be triggered if the relevant config option is present in the starship configuration.
Environment
Starship Configuration
The text was updated successfully, but these errors were encountered: