koanf VS urfave/cli

LINK: https://github.com/knadh/koanf

For configuration, I like Koanf.

Of course. You should always use a good config package. caarlos0/env is okay but https://github.com/knadh/koanf is a better all around solution imo.

You can also use Viper with urfave/cli, or you can replace Viper with knadh/koanf, which I personally prefer.

Use viper with care. It has some dangerous fundamental flaws [1]. We got bitten hard, submitted a PR [2] and followed up for a year and a half to no avail, before I went ahead and reinvented the wheel and wrote koanf (plug), specifically to avoid viper's flaws.

Most importantly:

- Breaks JSON, YAML, TOML etc. language specs by forcibly lowercasing all keys internally. Dangerous because it can silently merge differently cased config keys into lowercase.

- Hard codes big unnecessary dependencies into the core, significantly bloating build sizes. No separation or abstraction.

[1] https://github.com/spf13/viper/pull/635

[2] https://github.com/knadh/koanf#alternative-to-viper

It's not hard to a) look for a key in an environment variable b) accept a key as a parameter c) load a key from a file d) all of the above with something like koanf

Came across this the other day https://github.com/knadh/koanf as an alternative to Viper.

https://github.com/knadh/koanf for config management. Readme contains why it's a good alternative to viper.

Can you use a framework like urfavecli https://github.com/urfave/cli? This will auto-update every time it detects a new version from your CLI's GitHub repository

I use https://github.com/urfave/cli for local development over cli parameter inside docker over envs

....\Softwares\go\src\prysm\cmd\prysmctl\checkpointsync\cmd.go:3:8: cannot find package "github.com/urfave/cli/v2" in any of:

urfave/cli - A simple, fast, and fun package for building command line apps in Go;

and probably something else will be added in the future. The final kind of launch command would like to see such djob [options] - command. Command is the command (with arguments to run). -- should separate the arguments of the utility from the arguments of the program to run. There are several excellent solutions for working with command-line arguments, such as spf13/cobra or urfave/cli. But they’re good for building an interface out of a lot of commands, and for one (as in my example) they’re redundant. So I used the flag library. I have defined the following structure with arguments:

There are alternatives available for Cobra as well i.e. mitchellh/cli, go-flags, urfave/cli etc.

https://github.com/urfave/cli - A Golang package used to structure the CLI.