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
Unexpected switch-context
multi-select behaviour
#203
Comments
It’s on the “improvements” section of the changelog the intention was to make it faster to re-connect to previous clusters, but I can see how that’s annoying when switching clusters. for now, you can press ESC and it’ll clear the selection, but I’ll review this for the next minor release. Do you think the previous behaviour was better? |
Thank you for your awesome quick reply. to answer your questions:
In my opinion it was, when you do a "hard" select (like
I would honestly expect it to "skip" the select screen all togheter and just re-connect to the previously connected cluster(s). But it won't conflict with "quick" switching between clusters, So I don't mind.
Ah yes I noticed that once, but from the changelog it seemed only to affect on-startup. So didn't know it was expected behavior or not |
Hi @mikhail5555 I reverted this feature on 1.6.3 until I find a better way of doing it. |
Current and expected behavior
When using the
Switch Context
command, and going to the main screenExpected Behavior:
selecting an entry and then clicking Enter I would expect to only have that single cluster selected/connected.
Current Behavior:
But as the behaviour got changed in 1.6.2, it now adds the selected cluster to the "mutli cluster" feature, requiring manually deselecting all old clusters with space (which makes switching between two clusters pretty annoying.)
Also I don't see any mention of it in the changelog, so could it be it was an accidental change?
Environment & Operating System
macOS 13.6.3
aptakube: 1.6.2
Kubectl:
Client Version: v1.29.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.26.0
The text was updated successfully, but these errors were encountered: