-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat: allow for multiple plugin files in $XDG_DATA_DIRS/k9s/plugins #2029
feat: allow for multiple plugin files in $XDG_DATA_DIRS/k9s/plugins #2029
Conversation
dfbac9e
to
74e1255
Compare
Tests will follow 👍️ |
74e1255
to
7f4d0af
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwrau First off thank you so much Chris for this pr!
I really like the idea and especially the concept here in terms of sharing configurations across for all of us to use. This could extend to other artifacts beside plugins as well...
That said, I am not keen on the mechanics of the system wide location as this feels a bit as a departure from the current spec.
K9s uses xdg[https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html] to track its artifacts and I think it would be beneficial to continue on this directive. For instance we could leverage XDG_DATA_DIRS
to load extra configs if set. This would afford from allowing to extends k9s with plugins, themes, etc... that could be shared org wide.
One other thing this makes me think about, is instead of canning the plugins in an install tar ball, one could create a git repo to share these artifacts with co-workers/community folks as either public/private repos. This also provides a better upgrade path from single files to dirs.
Would this make better sense?
Sure, I can incorporate the I choose Maybe @ml- can shed some light on his reasoning? But in any way, our stuff isn't compiled, therefore
What do you mean by |
Back in 2020 when I created AUR packages for helm plugins, there was no existing package to use as reference and system wide installation of a plugin via package manager was not a use-case. So I consulted the ArchWiki on what the (more) correct place is for the files. Table over Arch_package_guidelines#Directories had the following hint:
file-hierarchy (7) and Filesystem Hierarchy Standard have further information on what files are expected in
|
Thanks for your input! I agree, I'm gonna implement that 👌 |
7f4d0af
to
26bf45b
Compare
26bf45b
to
9e02816
Compare
So, this should be about ready 👍️ |
@derailed, is there something I can do to get this rolling? 😁 |
@cwrau Did you see my review comments? |
Mh, not really 🤔 I've been trying to look at them but I can't find a way to show them. When I click on "view review", it just shows your comment. I thought that your requested changes were already superseded 😅 |
@cwrau Tx Chris! Sorry I am missing what you mean ;( |
I must be missing something, I can't for the life of me figure out how to view your requested changes 😅 See the attached video, I must be missing something 🥺 google_screen_recording_2023-05-08T08-50_20.529Z.webm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwrau Doh! it would have helped if I had pressed enter here. My bad ;( with feelings...
9e02816
to
ff00994
Compare
ff00994
to
435cbd0
Compare
@derailed I've resolved all your comments, is there something else to do? 😁 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwrau Tx for the updates! Just a minor pick..
435cbd0
to
30b2057
Compare
👋😉 |
30b2057
to
6aafb81
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwrau Thanks for the corrections Chris!
Heyho, is there a timeline for when we can merge this? 😁 I'm eagerly awaiting this feature! |
PingPong, just wanted to ask if there is something I can do to get this merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwrau Thanks for these updates Chris!
* 'master' of github.com:derailed/k9s: (130 commits) added flux suspended resources retrieval plugin (derailed#1584) Provide white blur so images work in dark modes (derailed#1597) Add context to get-all (derailed#1701) fix brew command in the readme (derailed#2012) Add support for using custom kubeconfig with log_full plugin (derailed#2014) feat: allow for multiple plugin files in $XDG_DATA_DIRS/k9s/plugins (derailed#2029) Clean up issues introduced by derailed#2125 (derailed#2289) Pod view resembles more the output of kubectl get pods -o wide (derailed#2125) Update README.md with snap install (derailed#2262) Add snapcraft config (derailed#2123) storageclasses view keeps the same output as kubectl get sc (derailed#2132) Fix merge issues with PR derailed#2168 (derailed#2288) Add colour config for container picker (derailed#2140) Add env var to disable node pod counts (derailed#2168) Use current k9s NS if new context has no default NS (derailed#2197) Bump actions/setup-go from 4.0.1 to 4.1.0 (derailed#2200) fix: trigger a single log refresh after changing 'since' (derailed#2202) Add crossplane plugin (derailed#2204) fix(derailed#1359): add option to keep missing clusters in config (derailed#2213) K9s release v0.28.2 ...
Closes #2028