-
Notifications
You must be signed in to change notification settings - Fork 263
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
Context sensitive Bash completion #1373
Comments
Let's add #1374 first and then continue with this story. |
Good point, let's keep this issue for tracking the overall story. |
Here are the smaller issues tracked by this issue: |
Sorry about the mess from too many PRs. I think we can reopen the issue and I can create subtasks for the remaining resources so this doesn't get closed before completion |
/reopen |
@dsimansk: Reopened this issue. In response to this:
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. |
/reopen |
@vyasgun: Reopened this issue. In response to this:
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. |
Feature request
kn completion
is currently based on the auto generation of the bash/zsh completion code by cobra. It lacks the the possibility to complete on context sensitive information likes service or revision names, something that e.g. kubectl allows.We should extend the completion code to allow completion on those resources. The way how
kubectl
does it could be taken as an inspiration.UI Example
would complete to "myservice" if there would be a Knative service installed that is called "myservice".
Here are the smaller issues tracked by this issue:
The text was updated successfully, but these errors were encountered: