Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Separate persistent from runtime configuration #3631

@jimonthebarn

Description

@jimonthebarn




Is your feature request related to a problem? Please describe.
I have put the k9s config directory into my dot files git repository in order to version my k9s configuration along with custom views and plugins, etc...
Among these settings k9s also stores the active namespace (k9s.namespace.active) and views (k9s.view.active) in the config.yaml per cluster which of course change whenever I switch either namespace or view within k9s. Git will naturally report the file as changed which is IMHO undesirable as this is not something I want to commit into a repository every time. The problem gets even worse the more clusters you manage.

Describe the solution you'd like
I would want to separate the parts of the configuration that are changed intentionally from the parts that get changed on-the-fly. Either separate them into separate files or maybe even simpler allow for the suppression of tracking the active view/namespace via configuration.

Describe alternatives you've considered
Currently im rolling back the config(s) every time it is changed but I'd much prefer to not have to do it.

Additional context
Not applicable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions