Skip to content
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

Feature request: support completion for sub-commands like switch, delete, rename #787

Open
nekomeowww opened this issue Oct 17, 2023 · 3 comments
Assignees
Labels
kind/feature ategorizes issue or PR as related to a new feature.

Comments

@nekomeowww
Copy link
Contributor

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.

@sunny0826
Copy link
Owner

Like the one shown below? This is the feature that has been implemented.

# Quick switch Kube Context
kubecm switch dev
# change to namespace of kube-system
kubecm ns kube-system

@nekomeowww
Copy link
Contributor Author

Yes. Does it? I do know that I could use kubecm switch minikube and kubecm switch dev to explicitly pass the context name argument in. But I was talking about implement the shell completion for these sub-commands (Not sure if we are aligned about the topic). I failed to ask it to prompt the completion for context names eventually. Did I missed any configurations and documentations?

@sunny0826
Copy link
Owner

Oh, not really, I misunderstood you.

@sunny0826 sunny0826 added the kind/feature ategorizes issue or PR as related to a new feature. label Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature ategorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants