Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration file precedence doesn't make sense. #296

Open
crayfishx opened this issue Nov 25, 2019 · 0 comments
Open

Configuration file precedence doesn't make sense. #296

crayfishx opened this issue Nov 25, 2019 · 0 comments

Comments

@crayfishx
Copy link
Contributor

From the docs;

Config files will be read first from /etc/eyaml/config.yaml, then from ~/.eyaml/config.yaml and
finally by anything referenced in the EYAML_CONFIG environment variable

This doesn't make a lot of sense, it is in fact documented wrong (see #295 ) as the config files are read in reverse order to what is documented... but having the variable EYAML_CONFIG read last (which is the case) doesn't seem to go with how most other software behaves.

I would expect that if I set an environment variable that should always override whatever is in a system wide default, rather than being a fallback... IMO the precedence should be

  • Environment Var
  • Home directory
  • System wide config.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant