Jira (HI-560) hiera() and lookup() performing merge by default

[Scott Nolin (JIRA)]

Title: Message Title

Scott Nolin created an issue   Hiera / HI-560 hiera() and lookup() performing merge by default Issue Type: Bug Affects Versions: HI 3.3.0 Assignee: Unassigned Created: 2017/03/07 1:55 PM Environment: Centos 7, puppet-agent-1.9.2-1, puppetserver-2.7.2-1, puppetlabs-release-pc1-1.1.0-5 Priority: Normal Reporter: Scott Nolin We migrated from puppet 3.8 to 4.9 I found that hiera() calls no longer default to the first value found for arrays and hashes. It instead now always does a merge. I tried using the new lookup() command, but it behaves the same. Our hiera.yaml is setup with :merge_behavior: deeper Which I read is now redundant. But that shouldn't affect the default behavior of lookup/hiera I tested by making simple hieradata entry in common.yaml - hieradata_test: foo Then in our node specific file set "bar" With this datatype it behaves as expected, reports the first entry - for us, 'bar', the node data. Then turned it into an array hieradata_test 'foo' In that case hiera('hieradata_test') returned Notice: /Stage[main]/Profiles::Hieradebug/Notify[hiera data test: [foo, bar]]/message: defined 'message' as 'hiera data test: [foo, bar]' I worked around this by changing all of our now 'surprising' calls like this to use lookup() and explicitly setting 'lookup_options' for each key type in common.yaml to 'merge: first'. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.