This is definitely a first world problem, and a very low priority feature request, but I think it could be really handy for new users to explore commands and for the other users to speed up their flow.
kubectl, kops, helm, and so many others all have this feature and I've grown quite fond of it.
They all follow the <programName> completion <shell> schema.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
I think it is more than a first world problem as it really increases productivity...
Command completion would be a very welcome addition.
My use case is switching from using kustomize build shipped in kubectl 1.14 (kubectl apply -k overlays/prod) to a standalone kustomize to use the latest version (v3.0.0) (kustomize build overlays/staging | kubectl apply -f -). I immediately felt the lack of command completion and a google search led me here. There are of course workarounds, aliases, scripts, etc. Having this work out of the box would improve quality of life.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Just dropping in to mention that thanks to #3110 this now works. E.g:
kustomize completion bash >/etc/bash_completion.d/kustomize
@ChrisEke Thanks! Didn't notice the release of the feature :tada:
Most helpful comment
Command completion would be a very welcome addition.
My use case is switching from using kustomize build shipped in kubectl 1.14 (
kubectl apply -k overlays/prod) to a standalone kustomize to use the latest version (v3.0.0) (kustomize build overlays/staging | kubectl apply -f -). I immediately felt the lack of command completion and a google search led me here. There are of course workarounds, aliases, scripts, etc. Having this work out of the box would improve quality of life.