simontheleg / konf-go Goto Github PK

When importing kubeconfigs it should be possible to use aliases for context and cluster. This makes it easier for users to use their own names to identify konfs, without the need to rename them first.

Handling in combination with the multi-kubeconfig feature from #43 tbd.

Taken from README.md

Be able to import all kube configs under a directory

Taken from README.md

Hiya 👋

With the following minimal .zshrc, My $KUBECONFIG variable is still not set after restarting the terminal.

.zshrc

# Konf
source <(konf-go shellwrapper zsh)
# Auto load context
export KUBECONFIG=$(konf set -)
# Autocompletion
source <(konf completion zsh)

Actual Output

Expected Output
$KUBECONFIG is set upon startup and automatically loads the default context so that it's ready to use.

ZSH: zsh 5.8.1 (x86_64-ubuntu-linux-gnu)
konf-go: "GitVersion":"0.5.1","GitCommit":"8ad03362b014b0ae5539dd6bd93c65d65ac15f7a","BuildDate":"2022-10-30T16:48:51Z","GoVersion":"go1.19","Platform":"linux/amd64","Compiler":"gc"}

Taken from README.md

When running konf ns the first namespace is highlighted even though that one is not necessarily the currently set namespace. It should have the currently selected namespace pre-selected. For example, see how kns works.

Hi, thank you for your job. A cool feature should to have an option in the set cmd to only show context name.
I send you a PR in this way.

Taken from README.md

version command is missing

Asking to fix package version at Nixpkgs.

Whenever I change context, the currently selected namespace is reset to the value set on import.

Ideally, the namespace would be updated in the store, so that later switches to the same context will continue in the same namespace.

This seems challenging, since we would have to commit changes to the store from a call to the current context.
Maybe this would not be interesting for everyone, so maybe make it a flag to konf namespace?

Taken from README.md

When you have no connection to a cluster, and run konf ns a blocking, but empty dialogue is displayed which only

Only after a while the error message appears:

Error: Get "<sanitized>/api/v1/namespaces": dial tcp <sanitized>: i/o timeout
Usage:
  konf namespace [flags]

Aliases:
  namespace, ns

Flags:
  -h, --help   help for namespace

Global Flags:
      --konf-dir string   konfs directory for kubeconfigs and tracking active konfs (default is $HOME/.kube/konfs)
      --silent            suppress log output if set to true (default is false)

Error: Get "<sanitized>/api/v1/namespaces": dial tcp <sanitized>: i/o timeout

Steps to reproduces:

1. Select a cluster which you cannot connect to
2. run konf ns

Expected behaviour:
Should display some hint, that we are attempting to connect to the cluster, before we display the empty dialogue.

It would be good to have a --move flag for the import cmd. This would then import the konf and after a successful import automatically delete the original file