It checks every layer of the hierarchy, so it would look for: fqdn/server1.yaml environment/staging.yaml common.yaml
But the important thing to know is it's looking for an actual variable. If you had defined selinux: disabled in common.yaml and nowhere else then it would always reach that file and pull in that value. Just because environment/staging.yaml matches the state of the machine doesn't mean it'll stop processing at that point - it'll check every file in the hierarchy it matches, in order, until it finds an entry for the variable you are looking up. (In a manifest you do $var = hiera(variablename)). On Tue, Apr 24, 2012 at 11:55 AM, Calimero <calimero...@evolutive.org>wrote: > > 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" ? > > -- 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.
