Is your feature request related to a problem? Please describe.
It is good to have such config management tool, how ever the current completion and cli design and implementation requires user to interactively navigate the options around when using sub-commands likeswitch, delete, rename. However, using both of interactive cli and completion is a bit of splitting my mind when native kubectl config use-context provides the cli interactive way with completion. Is it ok to provide both completion and interactive ways to select the target context? I'm happy to create and implement this feature.
Describe the solution you'd like
Provide both completion and interactive ways to select the target context.
Describe alternatives you've considered
None.
Is your feature request related to a problem? Please describe.
It is good to have such config management tool, how ever the current completion and cli design and implementation requires user to interactively navigate the options around when using sub-commands like
switch,delete,rename. However, using both of interactive cli and completion is a bit of splitting my mind when nativekubectl config use-contextprovides the cli interactive way with completion. Is it ok to provide both completion and interactive ways to select the target context? I'm happy to create and implement this feature.Describe the solution you'd like
Provide both completion and interactive ways to select the target context.
Describe alternatives you've considered
None.