What happened?
Since 3.18.x, plugins are checked and a WARNING is displayed to the output, not in stderr.
This leads to misbehavior with some commands whenever the env matchs the check
i.e
source <(helm completion bash) => fail
source <(helm completion bash)
-bash: /dev/fd/63: line 1: syntax error near unexpected token `('
-bash: /dev/fd/63: line 1: `WARNING: both 'platformCommand' and 'command' are set in "/home/kris/.local/share/helm/plugins/helm-secrets/plugin.yaml" (this will become an error in a future Helm version)'The workaround is
source <(HELM_NO_PLUGINS=1 helm completion bash)
What did you expect to happen?
The expected behavior is either
- write such warning in stderr
- provide a --quiet or --silent option
How can we reproduce it (as minimally and precisely as possible)?
source <(helm completion bash)
-bash: /dev/fd/63: line 1: syntax error near unexpected token `('
-bash: /dev/fd/63: line 1: `WARNING: both 'platformCommand' and 'command' are set in "/home/kris/.local/share/helm/plugins/helm-secrets/plugin.yaml" (this will become an error in a future Helm version)'Helm version
helm version
version.BuildInfo{Version:"v3.18.6", GitCommit:"b76a950f6835474e0906b96c9ec68a2eff3a6430", GitTreeState:"clean", GoVersion:"go1.24.6"}
Kubernetes version
N/A
What happened?
Since 3.18.x, plugins are checked and a WARNING is displayed to the output, not in stderr.
This leads to misbehavior with some commands whenever the env matchs the check
i.e
source <(helm completion bash) => fail
The workaround is
source <(HELM_NO_PLUGINS=1 helm completion bash)What did you expect to happen?
The expected behavior is either
How can we reproduce it (as minimally and precisely as possible)?
Helm version
Kubernetes version
N/A