On 24 avr, 15:34, Ashley Penney <apen...@gmail.com> wrote: > This was a long email!
Yeah, I know it might get a few "TL;DR" but I wanted to provided all relevant information. :) > The answer to your problems is definitely something > like > Hiera. You make a common.yaml that has all your "defaults" and then you can > overwrite these based on any fact you like, when building the hierarchy. > You can > make a hierarchy like: > > fqdn > environment > common.yaml That's the part I don't really get so far, as I haven't fiddled with Hiera yet. How would Hiera search through the hierarchy ? Try: fqdn/server1.yml ==> not found Try: environment/staging.yml ==> not found Fetch from common.yml Or: Try server1/staging.yml ==> not found Fetch from common.yml ie: is it "recursive" or it a list of "fallbacks" ? > Then you could make > > environment/staging.yaml > fqdn/server1.yaml I assume this matches matches my first example. Thanks for your help, G. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
