On Wed, Jan 9, 2013 at 3:11 AM, Luke Bigum <[email protected]> wrote: > > :backends: > - yaml > :hierarchy: > - %{fqdn} > - %{role}_role > - %{pop} > - global > :yaml: > :datadir: /etc/puppet/environments/%{environment}/hiera/ > > So if I push a new feature to branch new_feature, I get Puppet environment > "new_feature" which has it's own copy of the Hiera data store with all my > new_feature related Hiera keys in it. When it comes to environments my data > follows the same branches and "versions" of my code, and when I merge code > into my main line production branch the matching Hiera keys go along with > it.
Thanks, Luke. I guess it does make sense to leave the environments out of the hierarchy in this case. I had considered that, but was worried about constant merge conflicts when promoting things up the chain. There will be some things that will always be different between dev and prod. I suppose there are other ways around that though that make more sense. I may be inventing a problem I don't really have. -- Brad -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
