Skip to content

fix: Create plugin client with logger set to log level of PluginStore#182

Open
srager13 wants to merge 3 commits intodanielfoehrKn:masterfrom
srager13:set-plugin-loglevel-to-pluginstore-loglevel
Open

fix: Create plugin client with logger set to log level of PluginStore#182
srager13 wants to merge 3 commits intodanielfoehrKn:masterfrom
srager13:set-plugin-loglevel-to-pluginstore-loglevel

Conversation

@srager13
Copy link

@srager13 srager13 commented Jul 1, 2025

Fix for #181

When creating a plugin Client, create a Logger with the log level based on the log level of the PluginStore. Since these two resources use different log modules, add a function to convert the log level as closely as possible.

@guilhem
Copy link
Contributor

guilhem commented Aug 22, 2025

Gentle ping @danielfoehrKn :)

@srager13
Copy link
Author

Hi @danielfoehrKn , any chance you could take a look at this PR? It would really help our team's use of kubeswitch (which has been really useful, by the way, so thank you for creating and maintaining it!).

@academician
Copy link

academician commented Nov 13, 2025

Hate to be a pain, but @danielfoehrKn - I also ran into this problem. The plugin functionality actually works great except for this one issue, which causes logs to interfere with kubeswitch's TUI. This PR fixed the problem for me, but it would be nice not to work off of a fork.

If you'd like to test it, you can try the small plugin I just published to add kind entries to kubeswitch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants