When using the plugin kubeconfigStore type, the plugin Client that gets created does not configure the Client's logger, so the Client's logger uses the default log level of "Trace" set here: https://github.com/hashicorp/go-plugin/blob/a938e9a3385168c366e944d3c16a95a9a9b03d31/client.go#L420
Using the "Trace" log level prints a number of debug statements to stderr, so if a user does not redirect stderr output when running switch, the user interface gets ruined by these debug logs (see attached screenshot of terminal) making it impossible to see the valid context options and the sample kubeconfigs.
When using the
pluginkubeconfigStore type, the plugin Client that gets created does not configure the Client's logger, so the Client's logger uses the default log level of "Trace" set here: https://github.com/hashicorp/go-plugin/blob/a938e9a3385168c366e944d3c16a95a9a9b03d31/client.go#L420Using the "Trace" log level prints a number of debug statements to stderr, so if a user does not redirect stderr output when running
switch, the user interface gets ruined by these debug logs (see attached screenshot of terminal) making it impossible to see the valid context options and the sample kubeconfigs.