On Wednesday, April 29, 2015 at 8:25:17 AM UTC-5, Joseph Swick wrote: > > On 29/04/15 08:30, Dan White wrote: > > Have you tried plain YAML ? > > Your code looks OK, but I cannot be certain without tinkering. My > initial thought is that the eyaml backend may be to blame. > > So this is an issue I've run into on a couple of machines. As far as I > can tell, it's not eyaml, I found this reference to the issue with > relation to the automatic data bindings for hiera and hash merging: > > https://tickets.puppetlabs.com/browse/HI-118 > >
If you are talking about automated data binding then you threw us off by claiming that you were doing hash merging. You are not. Automated data binding uses only priority lookups, which is indeed the subject of HI-118. Some time ago I recorded my thoughts about that as a comment on that issue, and I will not repeat them here. At this point, however, if you want a hash-merge lookup then you must use the hiera_hash() function to get it. That's its whole point. > It's been a bit of an issue for a couple of machines for us. As far as > I've been able to tell, for where we do an actual heira lookup call it's > not affected, just for automatic bindings to parameters. > > It seems like you may be working under a distressingly common misconception: the choice between functions hiera(), hiera_array(), and hiera_hash() is not about the expected data type of the result; rather, it is about the lookup strategy: - The hiera() function performs an ordinary priority lookup, and it can return data of any type supported by Hiera. That certainly includes arrays and hashes. - The hiera_array() function performs an array-merge lookup to yield all values associated with the key from all levels of the hierarchy, in a flattened array form. At any given hierarchy level, the values do not have to be arrays. The overall result *is* an array, but that's not the point. You should not use this function to retrieve arrays if you want a standard priority lookup. - The hiera_hash() function performs a hash-merge lookups, the nature of which you seem to understand. Each value associated with the key at any hierarchy level must be a hash for this to make sense, but you should not use this function to retrieve hashes if you want a standard priority lookup. Priority lookup is Hiera's focus and default, and automated data binding uses that mode exclusively. If you want hash-merge lookup then you must call hiera_hash() explicitly in your manifest. John -- 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/c3de8c2f-a9a4-4164-83ec-fa53d61c02e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
