Stork agent cannot load environment file
The problem was reported on our mailing list.
Loading environment variables was removed from urfave/cli in the 2.16.6 version in the 3005438a1f3d1b67d2751da307463ddf4a5dd95b commit (change). It causes Stork not to load the environment file when the --use-env-file
flag is set.
Currently, the flag name passed to the context.Set
method must be a valid flag name.
Previously, any names were accepted. We used this behavior to set the raw environment variables from the environment file before parsing the flag values. The environment variables loaded this way were properly detected as standard environment variables.