You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing faas-cli, a bash alias faas is also created by creating a symbolic link according to the PR #234
Bash completion does not work for the alias faas though, which forces you to resort to using faas-cli
$ source /etc/bash_completion.d/faas
$ faas
auth deploy list namespaces secret version
build describe login new store
cloud generate logout push template
completion invoke logs remove up
But that's just something I have tested quickly on Linux.
Steps to Reproduce (for bugs)
Install faas-cli
Try auto-complete with faas with Tab
Context
Creating the faas alias without bash completion makes the alias not very useful as it makes you resort to faas-cli most of the time to get completion for the commands.
Your Environment
FaaS-CLI version ( Full output from: faas-cli version ):
After installing
faas-cli
, a bash aliasfaas
is also created by creating a symbolic link according to the PR #234Bash completion does not work for the alias
faas
though, which forces you to resort to usingfaas-cli
Expected Behaviour
Bash completion works for both
faas-cli
andfaas
Current Behaviour
Bash completion does not work for the alias
faas
.Possible Solution
There is a helpful guide in the cobra repo:
https://github.com/spf13/cobra/blob/master/bash_completions.md#using-bash-aliases-for-commands
Creating a file under
/etc/bash_completion.d/faas
on Linux with the content below would fix this:complete -o default -F __start_faas-cli faas
The completion works after sourcing that file
But that's just something I have tested quickly on Linux.
Steps to Reproduce (for bugs)
faas-cli
faas
with TabContext
Creating the
faas
alias without bash completion makes the alias not very useful as it makes you resort tofaas-cli
most of the time to get completion for the commands.Your Environment
faas-cli version
):docker version
):Linux Ubuntu 18.04
The text was updated successfully, but these errors were encountered: