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

[Robert Heinzmann (JIRA)]

Title: Message Title

Robert Heinzmann commented on PUP-7543   Re: Hiera 5 Hierarchy fails with the same name at multiple levels One more note. It would be great to inherit key settings from the global layer to the environment layer if not specified in the environment layer. This would allow for a config like this: 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" In this setup, the globally defined keys are used and this allows the Puppetmaster administrator to provide and manage keys and puppetmaster users, to only consume the "encryption" while not dealing with key location etc. (which may be transparent for the user). If an option is specified at an layer, this one whould be used (as described in this bug) 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.