readOnly: true in config.yaml doesnt get overriden by readOnly: false in cluster config

[arnoldyahad]

Hello,
Im currently using v0.30.8 and started to use k9s in readonly mode for most of production clusters.
Since we have a lot of production clusters i have set the main k9s/config.yaml readOnly configruation to true:
(by default, i want k9s to be readOnly, as we have much more prod than dev clusters)

k9s:
  liveViewAutoRefresh: false
  refreshRate: 2
  maxConnRetry: 5
  readOnly: true

and in my cluster config file k9s/clusters/something1/something2/config.yaml i set it to be false:

k9s:
  cluster: something2
  readOnly: false

i would expect it to overriden as the docs say https://k9scli.io/topics/config/ and have it be not readonly

  readOnly: false          # [New!] you can now single out a given context and make it readonly. Woof!

can you please tell if its by design (to not allow setting a cluster to be read-write if the general config is read-only)?

[derailed]

@arnoldyahad Thanks for reporting this Arnold! I've ran into this issue as well ;( Fix is on the way...

[derailed]

Fixed v0.31.0