-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Move shell completion generation into 'kubectl completion' command #23801
Move shell completion generation into 'kubectl completion' command #23801
Conversation
should any of the zsh glue stuff move into the cobra repo, for others? |
664f416
to
93998cb
Compare
Very good question. I reimplement a number of missing functions that are not part of the zsh completion environment to make it work, of course only as far as necessary for kubectl. This is not really a "just-works" situation for other programs based on cobra, depending especially on custom functions. Let me check in detail. |
@kubernetes/kubectl |
@sttts are you going to rebase this? did we land all the pre-reqs? |
@eparis will rebase |
93998cb
to
715e5d3
Compare
@ingvagabund @liggitt @deads2k please CC anyone else you know of who might get bitten by this.... |
On Mon, May 9, 2016 at 2:53 PM, Kubernetes Bot notifications@github.com
|
Rebased. |
f208125
to
3020465
Compare
3020465
to
9e25d9f
Compare
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 9e25d9f. |
Automatic merge from submit-queue |
Amen. |
We have moved the shell script into `kubectl completion` command in [kubernetes#23801](kubernetes/kubernetes#23801), updated the bash completion usage in the doc. Fixes kubernetes#1092
We have moved the shell script into `kubectl completion` command in [kubernetes#23801](kubernetes/kubernetes#23801), updated the bash completion usage in the doc. Fixes kubernetes#1092
We have moved the shell script into `kubectl completion` command in [kubernetes#23801](kubernetes/kubernetes#23801), updated the bash completion usage in the doc. Fixes kubernetes#1092
We have moved the shell script into `kubectl completion` command in [#23801](kubernetes/kubernetes#23801), updated the bash completion usage in the doc. Fixes #1092
…ource-error-message Bug 1743675: validations: for negative PVC storage size don't report "must be >= 0" Origin-commit: 164fc5b8b6ff3a8f911bdf6c8ca94a7666de9e3d
Remove static shell completion scripts from the repo and add
completion
command to kubectl:or
This makes maintenance easier because no static scripts must be generated and committed anymore in the repo.
Moreover, kubectl is self-contained again for the user including the latest completion code. I am thinking about the use-case of updating kubectl via gcloud (or some package manager). The completion code is always in-sync, without the need to download a
contrib/completion/bash/kubectl
file from github.Opinions are welcome /cc @eparis @nak3
Fixes openshift/origin#5290
This change is