Feature/initial view

[uozalp]

This pull request introduces a new configuration setting called initialView that allows users to specify the initial view in the application. The changes span across multiple files to integrate this new setting into the application logic, configuration, and documentation.

Configuration and Documentation Updates:

• README.md: Added a description of the initialView setting to the configuration section.
• internal/config/json/schemas/k9s.json: Added initialView as a new string type configuration option.

Application Logic Updates:

• cmd/root.go: Modified the run function to set the active view based on the initialView configuration if it is specified.
• internal/config/k9s.go:
  • Added InitialView as a new field in the K9s struct.
  • Updated the Merge method to include merging the InitialView field.

[uozalp]

Created a new pull request, because I messed up my git. Original PR: https://github.com/derailed/k9s/pull/2857

[uozalp]

@derailed ?

[KevinGimbel]

Hello there! Thank you for your PR and your work on k9s!

There is already a way of setting active views per cluster - in the cluster specific configuration file ( $XDG_DATA_HOME/k9s/clusters/clusterX/contextY/config.yaml) under k9s.view.active

k9s:
  [...]
  view:
    active: po

The problem here is: the value for the cluster specific config is automatically generated and sets the view to a default value (I think po). This would take precedence the k9s "main" config.

So to implement the initialView feature we'd need to rewrite the logic of looking up the configs or remove the auto-generation of a value (or make initialView take precedence over any cluster specific setting which feels odd.)

@derailed I think your input is required here as to make a decision how to proceed with this feature.

[uozalp]

@KevinGimbel I believe this behavior corresponds to the last active view for the cluster/context.

By default, K9s always starts in the last active view unless the --command flag is provided, which overrides it and takes precedence.

The changes proposed in this PR don't alter that behavior:

• If K9s is started without any flags, it will start in the last active view.
• If K9s is started with the --command flag, it will start in the specified view. If the flag is invalid, it falls back to the po view.
• If K9s is started with the initialView setting, it will start in that view. If the view is invalid, it will also fall back to the po view.
• If the initialView is configured and K9s is started with the --command flag, the --command flag will take precedence.

[uozalp]

@derailed have you had a chance to look at this?

[derailed]

@uozalp Also looks like we have some conflicts. Can you take a peek? Thank you!

[uozalp]

@derailed I have renamed it to defaultView and updated the PR

[uozalp]

I personally prefer the current behavior since we manage multiple clusters, and I like starting in the ctx view by default.

That said, there are cases where you might have a command like:

k9s -c deployment -n mynamespace --context mycontext

saved in your shell history. If you do a quick reverse search, you’d still want that command to take precedence, even if a default view is configured.

[uozalp]

@derailed I know you’re super busy, did you manage to review the PR? Anything else you want changed?