You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Some commands like ctrl-d is not revokable but could be run by accident without any obstacle, in production cluster.
Describe the solution you'd like
Provide CONFIRM_BEFORE_DESTRUCTIVE_ACTION option(flag).
If this option is enabled, every descructive actions (e.g., drain, delete, kill, ...) make popup appear, and only exeucted if user move focus box and hit enter.
Describe alternatives you've considered
First time I thought that I could avoid this trouble by making this key bindings to impossible combination like ctrl-d-y-u-p-n, but AFAIK it's not possible to change default keybindings. source
Additional context
.
The text was updated successfully, but these errors were encountered:
In addition to CONFIRM_BEFORE_DESTRUCTIVE_ACTION, provide --confirm-destructive via cli args. (similar usage to --readonly)
On destructive action, make a popup appear with a text field that requires the user to type 'delete', then move focus to OK option before hitting enter.
This extra required input should interrupt the muscle memory of ctrl-d, TAB, enter and prevent accidents. Plus, users can alias k9c="k9s --confirm-desctructive" for quick access when accessing sensitive environments like production and want an extra layer of safety.
Is your feature request related to a problem? Please describe.
Some commands like
ctrl-d
is not revokable but could be run by accident without any obstacle, in production cluster.Describe the solution you'd like
CONFIRM_BEFORE_DESTRUCTIVE_ACTION
option(flag).Describe alternatives you've considered
First time I thought that I could avoid this trouble by making this key bindings to impossible combination like
ctrl-d-y-u-p-n
, but AFAIK it's not possible to change default keybindings. sourceAdditional context
.
The text was updated successfully, but these errors were encountered: