Jira (PUP-7543) Hiera 5 Hierarchy fails with the same name at multiple levels

[Jarret Lavallee (JIRA)]

Title: Message Title

Jarret Lavallee created an issue   Puppet / PUP-7543 Hiera 5 Hierarchy fails with the same name at multiple levels Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Components: Hiera & Lookup Created: 2017/05/16 9:28 AM Environment: PE 2017.2.1 with Hiera 5 with eyaml backend Priority: Normal Reporter: Jarret Lavallee When using Hiera 5 with the same Hierarchy file name at the global and environment level, lookups fail to use the options associated with the global level It appears that the global file path is used, but the environment options are used. When using eyaml, this results in using the wrong keys on the eyaml file. Example Global hiera.yaml --- version: 5 defaults: datadir: data   hierarchy: - name: "Global secrets" lookup_key: eyaml_lookup_key path: "secrets.eyaml" options: pkcs7_private_key: /etc/puppetlabs/puppet/keys/private_key.pkcs7.pem pkcs7_public_key: /etc/puppetlabs/puppet/keys/public_key.pkcs7.pem Environment hiera.yaml --- version: 5 defaults: datadir: data   hierarchy: - name: "Environment secrets" lookup_key: eyaml_lookup_key path: "secrets.eyaml" options: pkcs7_private_key: /etc/puppetlabs/code/environments/production/keys/private_key.pkcs7.pem pkcs7_public_key: /etc/puppetlabs/code/environments/production/keys/public_key.pkcs7.pem Looking up a key which is both the environment and global secrets.eyaml # puppet lookup secret --explain Error: Could not run: bad decrypt Looking up a nonexistent key # puppet lookup doesnotexist --explain Searching for "doesnotexist" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Global secrets" Path "/etc/puppetlabs/puppet/data/secrets.eyaml" Original path: "secrets.eyaml" No such key: "doesnotexist" Environment Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml" Hierarchy entry "Environment secrets" Path "/etc/puppetlabs/code/environments/production/data/secrets.eyaml" Original path: "secrets.eyaml" No such key: "doesnotexist" Function lookup() did not find a value for the name 'doesnotexist' An environment specific key works when not defined in the global eyaml file. # puppet lookup envsecret --explain Warning: Unknown variable: 'creates_path'. at /opt/puppetlabs/puppet/modules/pe_staging/manifests/extract.pp:56:22 Searching for "envsecret" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Global secrets" Path "/etc/puppetlabs/puppet/data/secrets.eyaml" Original path: "secrets.eyaml" No such key: "envsecret" Environment Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml" Hierarchy entry "Environment secrets" Path "/etc/puppetlabs/code/environments/production/data/secrets.eyaml" Original path: "secrets.eyaml" Found key: "envsecret" value: "environmentsecret" A global specific key fails # puppet lookup globalsecret --explain Error: Could not run: bad decrypt Steps to Reproduce Install 2017.2.1 Install eyaml Configure the global hiera.yaml as above Create eyaml keys for the global eyaml Create encrypted keys in the global data/secrets.eyaml Configure the environment hiera.yaml as above Create eyaml keys for the environment eyaml Create encrypted keys in the environment data/secrets.eyaml Lookup keys defined in the global secrets.eyaml Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.