warpdotdev
kubectl --context completions are not working in warp.dev shell.
Dupe Check
- [X] I have searched Warp bugs and there are no duplicates
Describe the bug
Completions are not working for the --context switch. The completions below are showing the file listing instead of the k8s contexts.
If the context is manually typed, then the completions for the following switches (like namespace) should be filtered based on selected context switch in the current command line. However, it is displaying the completions based on the current context in the shell.
To reproduce
- In warp.dev shell type the following and then press tab:
kubectl get --context
Expected behavior
I would expect to see a list of the contexts within the ~/.kube/contexts directory similar to this:
Screenshots
No response
Operating system
MacOS
Operating system and version
macOS 14.5
Shell Version
fish, version 3.5.1 But have tried with GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin23)
Current Warp version
v0.2024.07.23.08.02.stable_01
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
I noticed that --cluster switch completions also do not work. Very similar to --context.
Thanks for letting us know @bunn-turnera We're aware that some combinations of kubectl and certain flags don't currently complete correctly in Warp. You may be able to fallback to shell completions by running fish(or zsh) in a subshell, as a possible workaround. We'll post any updates on this thread.
To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.
Has there been any thoughts on prioritizing this bug? Warp has been a great tool. However, most of my time in a terminal is spent interacting with Kubernetes and since I have to manage multiple clusters this feature would be very useful for me.
Thanks.
I also love Warp but this bug is super frustrating. Any hope this bug will get fixed?
