We have a "tab completion" ability in istioctl. This saves typing for long commands such as "istioctl experimental verify-install".
We have a mechanism to generate the bash config file, istioctl collateral --bash. But the command is hidden so users don't see it and we don't document it.
I produced a PR to make this option visible, possibly with a new name, but the feedback on that PR was that we shouldn't have people create the file. Instead we should provide it as part of our builds, and document how users should get it.
For example, for git tab completion see this post https://git-scm.com/book/en/v1/Git-Basics-Tips-and-Tricks where users are shown how to download the file and set it up.
We have a "tab completion" ability in istioctl. This saves typing for long commands such as "istioctl experimental verify-install".
We have a mechanism to generate the bash config file,
istioctl collateral --bash. But the command is hidden so users don't see it and we don't document it.I produced a PR to make this option visible, possibly with a new name, but the feedback on that PR was that we shouldn't have people create the file. Instead we should provide it as part of our builds, and document how users should get it.
For example, for
gittab completion see this post https://git-scm.com/book/en/v1/Git-Basics-Tips-and-Tricks where users are shown how to download the file and set it up.