Feature Suggestion — Check arbitrary keys/values about envconfig HOT 5 CLOSED

I had some feedback on the PR, but @CAFxX you're way ahead of me here. Great suggestions, thank you.

from envconfig.

PR submitted. Suggestions welcome.

from envconfig.

I don't understand the requirement. If you want to protect against forgetting to add the environment variables in production, can't you simply mark the fields as required?

from envconfig.

@CAFxX We do that, but the issue we have is that we have to start up the service with each environment's config file in order to see the missing values. And in some cases we'd rather not start a service with production config, as it might start consuming from queues, for example.

from envconfig.

Wouldn't having a dry-run/config validation flag that instructs the process to exit immediately after parsing its configuration be the simple and easy solution, then?

func main() {
  cfg := &Config{}
  if err := envconfig.Parse(cfg); err != nil {
    // Fatal(err)
  }

  // perform here any additional config validation, erroring out if it fails...

  if cfg.DryRun {
    os.Exit(0)
  }

  // actual program logic...
}

Alternatively, why can't you produce a parseable dump of the list of known envvars using Usagef/Usaget, and then use it during your build process to validate whatever preconditions have to be met for a successful build?

from envconfig.