argparse VS urfave/cli

Nice to find that golang has this tool (I found only argparse adaptation https://github.com/akamensky/argparse). For me, as newcomer, flag is soooo basic. The reason why I still stick with it, because standard approach is more important for my use case, which is one layer upper than single language best parser. I am doing the same thing for various languages to make argument parsing be as easy as configuration change (if you are curious see https://github.com/ashlander/protoargs). That does not exclude potential Kong usage as an alternative backend at some point

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.