-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
bash autocompletions are not packaged into our binaries #5290
Comments
If we're going with the suggestion in the description this is a hack/build-go.sh and golang fix un-related to the installer. I think this should be assigned to the UI/CLI team. |
@smarterclayton Please provide a replacement priority. |
@fabianofranz Any thoughts on bundling completions for users who download the client only? |
I assume we're just going to have an oc config autocomplete or something? On Nov 21, 2015, at 6:00 PM, Scott Dodson notifications@github.com wrote: @fabianofranz https://github.com/fabianofranz Any thoughts on bundling — |
|
not sure I want |
Agree - being able to source an autocomplete file is probably all we should On Nov 23, 2015, at 10:01 AM, Jordan Liggitt notifications@github.com not sure I want login to do that... config file is within it's set of — |
Reopening, unless I missed it this was fixed in Kube is still pending a new Kube rebase into origin. |
Didn't realize Kube PRs could auto-close Origin issues... |
Fixed by #9354 |
We should package our autocompletions into our releases. It would be nice if they were compiled into the binary and the binary would check for them in the user's home directory and place them if they're not found or outdated.
@sdodson
The text was updated successfully, but these errors were encountered: