search

vmware-archive / octant

Highly extensible platform for developers to better understand the complexity of Kubernetes clusters.
https://octant.dev
Apache License 2.0
6.28k stars 488 forks source link

octant Delete Plugin #517

Open danielhelfand opened 4 years ago

danielhelfand commented 4 years ago

Currently, you must run rm ~/.config/octant/plugins/<plugin name> to remove a plugin. It would be nice to be able to remove a plugin via the CLI instead so users don't have to remember the location of where plugin binaries are located.

The idea would be something along the lines of octant delete plugin <plugin name> would remove the plugin binary. Then that plugin will not be available when restarting Octant.

wwitzel3 commented 4 years ago

Having some mechanism for getting at installed plugins is a good idea. I think having CLI commands could work, maybe in combination with having a button in Octant that opens the plugin folder using the system file browser.

GuessWhoSamFoo commented 4 years ago

Plugin management as a whole should be added to the roadmap as it is something that should exist in 1.0

danielhelfand commented 4 years ago

@GuessWhoSamFoo Agreed. Something to also install plugins I think would be nice long term.

I think the CLI makes the most sense as the way for users to manage plugins since plugin changes require a restart anyway. Doing it through the UI might be misleading as to why something isn't added or removed.

wwitzel3 commented 4 years ago

We would like to remove having to restart to load/unload plugins as well #178 , which ties in to what @GuessWhoSamFoo is saying about having a good plugin story as part of our 1.0 roadmap.