Skip to content
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

plugin does not install if helm is helm 3 but run from helm 2 #244

Closed
schollii opened this issue Nov 2, 2020 · 8 comments · Fixed by #307
Closed

plugin does not install if helm is helm 3 but run from helm 2 #244

schollii opened this issue Nov 2, 2020 · 8 comments · Fixed by #307
Labels

Comments

@schollii
Copy link

schollii commented Nov 2, 2020

The install-binary.sh script uses the helm home command which only exists in helm 3. Interestingly, if either helm 2 XOR helm 3 are installed on my system, the plugin installs fine. However if both versions of helm are on my system, and helm is actually helm 3, and helm 2 has some other name, then the plugin no longer installs for helm 2:

  • helm version shows helm 3
  • helm plugin install https://github.com/databus23/helm-diff works
  • helm2 version shows helm 2
  • helm2 plugin install https://github.com/databus23/helm-diff fails with error message that home is not a recognized command

At first unclear what this is about, but inspection of source code indicates the error happens because install-binary.sh calls helm home, which in the above scenario actually calls helm 3, which does not support home command (I'm guessing that helm 3's plugin install does not use that script otherwise it would fail too).

Is there a reason that $(helm home) cannot be replaced by $HELM_HOME?

@stale
Copy link

stale bot commented Feb 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 2, 2021
@schollii
Copy link
Author

schollii commented Feb 2, 2021

I'd like to keep this open. I'll submit a PR and see what happens.

@stale stale bot removed the stale label Feb 2, 2021
@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 2, 2021
@schollii
Copy link
Author

schollii commented Jun 2, 2021

bump

@stale stale bot removed the stale label Jun 2, 2021
@mumoshu
Copy link
Collaborator

mumoshu commented Jun 2, 2021

@schollii I think #270 fixed this issue. Would you mind confirming?

@schollii
Copy link
Author

schollii commented Jun 3, 2021

It looks like it might but I have to try it to be sure. I will post result soon.

@stale
Copy link

stale bot commented Sep 3, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@schollii
Copy link
Author

Looks like #270 fixes this indeed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants