-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Helm Diff path issue #316
Comments
I also have the following error while installing the plugin in version 3.1.3: > helm plugin install https://github.com/databus23/helm-diff
Error: exec: "sh": executable file not found in %PATH% This is related to helm/helm#7117. |
To install the help-diff plugin on Windows:
|
Not working for me. Its saying the same as OP: |
That's because there is a space in your path. Check your helm configuration or the plugin's one to identify and fix the issue, but I don't know how to do this |
As @srilumpa has mentioned in the prev comment, helm/helm#7117 seems to indicate that helm plugins isn't supported on Windows (yet). In the meantime, you would be able to run the plugin directly, by cloning the repo and running
Let me close this as answered and there isn't actionable from the helm-diff side. But please feel free to report back here if the direct run workaround doesn't work. |
I had a need to run helm-diff as part of a helmfile deployment, which wasn't able to use the direct run workaround. I was able to resolve this by copying the built I don't really understand all the moving parts here, but given a Windows build is published in the latest release and other helm plugins have managed to support Windows installation (e.g. helm-secrets) via |
My workaround
|
I think the support has been added recently so can the plugin add the windows support too? |
ok |
Hello,
I've just found Helm Diff and installed on my Windows 10 pc using
helm plugin install https://github.com/databus23/helm-diff
Calling
helm diff
from terminal ends like thisHelm installed from Chocolatey
The text was updated successfully, but these errors were encountered: