konf: init at 0.2.0

[arikgrahl]

Description of changes

konf is a lightweight kubeconfig manager. With konf you can use different kubeconfigs at the same time. And because it does not need subshells, konf is blazing fast!

-- https://github.com/SimonTheLeg/konf-go

See #190758

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.11 Release Notes (or backporting 22.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[azahi]

Also, I would advise you not to change the upstream name where possible. We probably should go with konf-go instead of konf.

[arikgrahl]

Also, I would advise you not to change the upstream name where possible. We probably should go with konf-go instead of konf.

Picking konf instead of konf-go was intentional.
Konf consists of a Go binary, which is referred to as konf-go, and a corresponding shell wrapper, which is essentially the shell function konf.
The Go binary is not intended to be invoked directly, only through the particular shell function.
I guess the name konf-go was therefore only introduced to differentiate the shell function from the binary.

However, in this Nix package konf should be eventually bundled completely, covering both the Go binary and the shell function.
I would consider the integration of the latter as a follow-up issue.

Therefore, I am convinced that konf suits as the name the best.
If there are any doubts or background information lacking, I am happy to reach out to the author of the upstream project.