On Wednesday, October 30, 2013 10:08:14 PM UTC+9, jcbollinger wrote: > > Per the docs, the :merge_behavior setting affects how hashes are merged in > a "hash merge lookup". Not every hiera lookup is a hash merge lookup, and > whether a query is of that kind does not depend on the type of the data > retrieved. A standard hiera lookup, such as is performed by the ordinary > hiera() function, simply returns the highest-priority datum it finds in the > data hierarchy. This is what is used for automated class parameter > binding. A hash merge lookup, on the other hand, is what you get from the > hiera_hash() function. >
Makes sense. I think that the confusion stems from using on hiera_include's array merge lookup, seeing your class arrays being merged nicely and assuming such behaviour extends to class parameter binding. I understand the reasons maintaining priority lookup for class parameters though. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b8d4d310-e1c2-4e36-9c2e-b1ffe157a3bd%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
