-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Support @ sign in context names. #145
Comments
Huh, interesting. Any ideas why @ is treated as a separator? Also, zsh or bash completion? |
I'm using bash. I haven't poked too much into it, I'm guessing '@' is treated as a word separator by default but I don't know where that decision is made. |
Has it been fixed ? I've no issue with Bash and |
@loganmzz Can you confirm by "no issue", you mean you're generating the autocompletion and using it via tab successfully? |
Yes all my context names contains a |
Perfect! |
In many environments it's common to have different roles authenticating to the same cluster. This generally results in contexts named "developer@cluster-1" or "admin@cluster-1", etc.
The current completion scripts do not properly digest the '@' sign (treating it as a separator).
The text was updated successfully, but these errors were encountered: