K9s: Disable read only config via command-line flag

[wayneashleyberry]

Is your feature request related to a problem? Please describe.

I currently have the ability so put k9s in read only mode from a config file stored in ~/.k9s/config.yml, which is great because that's the default behaviour I'd like. There is however no way to temporarily disable it, for those few times when I do actually want to make changes to a cluster.

Describe the solution you'd like

A command-line flag that would take precedence over the value set in the config file could work, either for enabled "write mode" or disabling read only.

eg.

k9s --write
k9s --read-only false

Describe alternatives you've considered

I am manually disabling readOnly in the config file when I need to make edits.

[derailed]

@wayneashleyberry I think this option is already available ie

# Override default configuration by passing either --readonly or --readonly=false
k9s --readonly=false

[wayneashleyberry]

@derailed that doesn't work for me, it's very clear to see because the <ctrl-d> shortcut key disappears in the header

[derailed]

@wayneashleyberry Thank you for the correction Wayne! I see it now. Will fix in the next drop.

[derailed]

@wayneashleyberry Fixed v0.23.1. I think...

[wayneashleyberry]

I think a different regression has been introduced now @derailed — the readOnly value set in my config file isn't being respected now. Tested the latest version and with readOnly set to true, running k9s lets me delete things.

~
❯ cat .k9s/config.yml | grep read
  readOnly: true

~
❯ k9s
 Context: staging                                              <0> all       <a>      Attach     <l>       Logs                  ____  __.________
 Cluster: ***_****-**rv*c**_u*-***t1-d_*v*r-*p*-*t*g**g-3      <1> default   <ctrl-d> Delete     <p>       Logs Previous        |    |/ _/   __   \______

[derailed]

@wayneashleyberry Sorry! Please checkout v0.23.3 --write cli arg. Thank you for catching me on this!

[wayneashleyberry]

Perfect! Thank you so much @derailed 🙌