Feature Request: Helm Context Menus
See original GitHub issueIt would be great if there are context menus on Helm Resources.
Currently Helm Releases
lists helm releases it would be really useful to have context menus like Status
, History
, Rollback
Uninstall
in the context menu of a helm release.
Happy to submit a PR for this if this is something that would be considered helpful. If there is interest in adding the context menus, what would be a good place to start?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Feature Request: Helm Context Menus · Issue #748 · vscode ...
Currently Helm Releases lists helm releases it would be really useful to have context menus like Status , History , Rollback Uninstall in...
Read more >Introduction to Helm: Charts, Deployments, & More - Harness
Helm was designed to be the first package manager for Kubernetes. Learn everything that you need to know about Helm with Harness.
Read more >Helm Repositories - Sonatype Help
Nexus Repository functions with both Helm2 and Helm3. You can publish your own charts and provenance files to a private repository in a...
Read more >IntelliJ IDEA 2018.3: Helm support - The JetBrains Blog
Choose the new Kubernetes | Helm Template action from the context menu, and the IDE will preview the result of the Helm template...
Read more >Announcing: install applications with the Helm CLI using ...
Functionality in the admin console is updated so that Helm rather than KOTS manages the lifecycle of the application.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let’s wait some day and see if @itowlson answers, maybe he already have an idea on this. I guess he’s very busy so hopefully beginning next week he will come back. I’ll ping him.
BTW if you find the second option the most valuable just go for it and create a PR, maybe i’ll change my mind once i try that 😃
I would love to see a PR for this - thanks!
In terms of where to start, not sure if you are asking about which command(s) to start with, or the technical aspects. You’ve already done a lot of work on this extension already, so I’m guessing the former, because you probably know your way around the technical side! (But happy to offer guidance if you do want it.)
I agree it would be best to PR just one or two initially, and then do the rest when we had worked through any design considerations. My suggestions would be Rollback and Uninstall because those probably require less output than Status or History so you don’t need to get tangled up in webviews or stuff…?