-
Notifications
You must be signed in to change notification settings - Fork 44
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
Support for multiple Kubel buffers, each one using a different combination of Contex, Namespace, Resource, Filters, and Labels. #57
Conversation
- Kubel mode is only set once when the buffer is created. - Now when `kubel` is called, it'll always create a new buffer with fresh variables for - context, namespace, and resource. - Stop killing existing buffer when changing objects, instead, a new function - `kubel-refresh` is now taking care of displaying/refreshing current configuration. - Show a message when the command is being executed, to easily tell if a command is being executed.
When there are too many kubel buffers is hard to differentiate what buffer belongs to an specific cluster/namespace
I added pipe and colon to buffer name, pretty sure that will not work in Windows
It wasn't taking into account parent cluster,buffer from where it was created
Hey @abrochard I added some more commits to fix an issue regarding kubectl apply (it wasn't working as I wasn't passing the context/namespace). |
Please 👀 and test, as most of the time I work on a different version of this package (different caching, single kubel process and err buffer process, I also plan to send some PRs after this gets 👍 or 👎), I only use this branch to send upstream changes. |
<img src="https://screenshot.click/16-00-e54eg-wgzaz.png" width="50%" />
I merged latest master on top of the branch. |
README.md
Outdated
@@ -54,6 +55,11 @@ M-x kubel-set-resource | |||
``` | |||
This will let you select a resource and re-display the kubel buffer. | |||
|
|||
You can also use `kubel-open` to open directly a kubel buffer with the given parameters, example: | |||
``` lisp | |||
(kubel-open "custom-context" "custom-namespace" "custom-resource")) |
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.
big fan of this
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.
I'm using it every day, you get a lot of time back as you don't need to wait for getting the list of context, list of namespaces and get list of pods, you can go directly to where you're interested.
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.
Yeah it's really sweet. I'm also gonna hook it up to magit post-commit or something so I can monitor my deployment once I push a release.
I don't use tramp, so not sure if this is needed
Hi @d1egoaz ,
I feel that pressing |
Thanks for the feedback. Let me try to review this again, I'll stop working on my personal/work branch and just move to use this PR branch so I can be fully committed with this change. I was able to confirm the bug, let me try to find the 🐛 |
Huh, for some reason If I run going to check what did I do with the keybindings |
I'm not sure why That said, I'm using a different key for refreshing the kubel session, as I found that I needed It'd be great in a future PR to follow the evil collection guidelines regarding the keys that might be used I just sent a PR with the fix, s/g/x |
Hmm I'm really not a fan of updating the binding. I don't use |
yeah, sorry about that, I don't use the normal mode, I'll make the change only for evil, I just pushed a new commit |
🤔 if you're not using evil, I wonder how did you hit the bug? unless it's breaking for some other reason. When you have some time please check the bindings on your side to see what' the values for |
Hey @d1egoaz , Sorry for the super late reply! I did another test of this just now, and there's definitely something weird on my side when loading the code and I need to manually force refresh the mode map. After I do, the However, even after doing that, I see some weird behavior when I switch context.
|
Hey, I'm close this for now, I've been OOO and OOC (computer) for several months as I was on paternity leave. I'll try to replicate your issues on my side, I used this fork for months without issues, I'd like to test on a vanilla emacs without my configuration to see if that's the issue. I'll try to return here in some months with a validated PR. Thanks |
* Multi buffers support (take #57 and rebase) * Add kubel--read-buffer, improve kubel-refresh and kubel command --------- Co-authored-by: Diego Alvarez <[email protected]> Co-authored-by: Adrien Brochard <[email protected]>
Add support to have multiple and functional kubel buffers, each one using a different combination of Contex, Namespace, Resource, Filters, Labels, last command,
Closes #54
Some notes:
kubel
is called, it'll always create a new buffer with fresh variables forkubel-refresh
is now taking care of displaying/refreshing current configuration.is being executed.