Jira (PUP-6943) control ordering of classic Hiera versus environment data searching

[James Ralston (JIRA)]

Title: Message Title

James Ralston commented on PUP-6943   Re: control ordering of classic Hiera versus environment data searching It feels hackish, but I believe your suggestion would work. For example, right now, in our global (version 3) hiera.yaml file, we have: :yaml: :datadir: /etc/puppetlabs/code/hiera :hierarchy: - nodes/%{fqdn}/config - ./%{hiera_area_0}/config - ./%{hiera_area_1}/config - ./%{hiera_area_2}/config - ./%{hiera_area_3}/config - ./%{hiera_area_4}/config - ./%{hiera_area_5}/config - ./%{hiera_area_6}/config - ./%{hiera_area_7}/config - ./%{hiera_area_8}/config - ./%{hiera_area_9}/config - ./%{hiera_area_10}/config - ./%{hiera_area_11}/config - ./%{hiera_area_12}/config - ./%{hiera_area_13}/config - ./%{hiera_area_14}/config - ./%{hiera_area_15}/config - all/config (The hiera_area_* facts are custom facts that are exported from the host—essentially, a poor man's ENC.) If I create a hiera-global symlink in each environment that points to /etc/puppetlabs/code/hiera: $ cd /etc/puppetlabs/code/environments $ ( for D in *; do ln -s ../../hiera "${D}/hiera-global"; done ) …then I can change our global hiera.yaml file to: :yaml: :datadir: /etc/puppetlabs/code/environments/%{environment}/hiera-global Then after I copy the global Hiera data into the environment, I simply remove the hiera-global symlink from that environment. For all hosts in that environment, the version 3 hiera.yaml's datadir setting will now point to a non-existent directory, ensuring all global Hiera data lookups will miss. When we (eventually) convert all environments to environment data, then we can wipe the global Hiera data clean, and restore the original datadir setting in the version 3 hiera.yaml file. At that point, the global Hiera data can assume its "emergency override" purpose. Can you see any flaws in this approach, or suggest any improvements? (Speaking a sysadmin who also does a fair amount of development, I can appreciate not wanting to make already-complicated code even more complicated just for the sake of a temporary migration, so I'm willing to use this approach to migrate—as long as there aren't any hidden gotchas that I'm not seeing.) 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.