(doc) Correct order for config file precedence

[crayfishx]

The documentation states that the file /etc/eyaml/config.yaml is read first, and then falls to ~/.eyaml/config.yaml. This would be an odd way to resolve config as local users normally take priority over global settings, and a quick test proves this isn't the case and the README is wrong....

Using just a global config.yaml

[vagrant@puppet .eyaml]$ cat /etc/eyaml/config.yaml
pkcs7_private_key: /etc/puppetlabs/puppet/eyaml/private_key.pkcs7.pem
pkcs7_public_key: /etc/puppetlabs/puppet/eyaml/public_key.pkcs7.pem

[vagrant@puppet .eyaml]$ /opt/puppetlabs/puppet/bin/eyaml encrypt -s foo
string: ENC[PKCS7,MIIBeQYJKoZIhvcNAQcDoIIBajCCA......

Placing a (broken) config.yaml in ~/.eyaml

[vagrant@puppet .eyaml]$ mv ~/.eyaml/config.yaml_ ~/.eyaml/config.yaml && cat ~/.eyaml/config.yaml
pkcs7_private_key: /etc/puppetlabs/puppet/eyaml/private_key.pkcs7.pem_HOMEDIR
pkcs7_public_key: /etc/puppetlabs/puppet/eyaml/public_key.pkcs7.pem_HOMEDIR

[vagrant@puppet .eyaml]$ /opt/puppetlabs/puppet/bin/eyaml encrypt -s foo
[hiera-eyaml-core] No such file or directory @ rb_sysopen - /etc/puppetlabs/puppet/eyaml/public_key.pkcs7.pem_HOMEDIR

Conclusion

The config.yaml in my homedir is being read first and takes priority which contradicts the docs.

[bastelfreak]

thansk for figuring this out @crayfishx !