Jira (HI-283) native, deep, or deeper merge not working as expected

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: native, deep, or deeper merge not working as expected You're not seeing the data merged in because the node/%{::fqdn} variable isn't being set. If we do a normal priority lookup and the lookup was working, we should see the node specific value but we don't: [vagrant@centos65 ~]$ hiera -c /vagrant/puppet/hiera.yaml mymodule::options {"param1"=>"param1", "param2"=>"param2", "param3"=>"param3", "param4"=>"param4", "nested"=> {"param1"=>"nested_param1", "param2"=>"nested_param2", "param3"=>"nested_param3", "param4"=>"nested_param4"}} This is because the ::fqdn variable isn't set. If we specify that on the command line as part of the scope we get the correct priority lookup: [vagrant@centos65 ~]$ hiera -c /vagrant/puppet/hiera.yaml mymodule::options ::fqdn=centos65.vm.local {"nested"=>{"param4"=>"new_nested_param4"}} And if we do that lookup with the scope and use a hash lookup, we see the deep merge occurring: {"nested"=> {"param1"=>"nested_param1", "param2"=>"nested_param2", "param3"=>"nested_param3", "param4"=>"new_nested_param4"}, "param1"=>"param1", "param2"=>"param2", "param3"=>"param3", "param4"=>"param4"} When running hiera on the commandline, there is no scope set up by default. Since you're using a fully qualified variable name we can't directly dump the output of Facter and use it as the scope, but if you change ::fqdn to fqdn then you can use Facter as the scope input: --- :backends: - yaml :hierarchy: - nodes/%{fqdn} # Note the omitted double colon - common :yaml: :datadir: /vagrant/puppet/hieradata :merge_behavior: deeper [vagrant@centos65 ~]$ facter -y > scope.yaml [vagrant@centos65 ~]$ hiera --hash -c /vagrant/puppet/hiera.yaml --yaml scope.yaml mymodule::options {"nested"=> {"param1"=>"nested_param1", "param2"=>"nested_param2", "param3"=>"nested_param3", "param4"=>"new_nested_param4"}, "param1"=>"param1", "param2"=>"param2", "param3"=>"param3", "param4"=>"param4"} Add Comment   Hiera / HI-283 native, deep, or deeper merge not working as expected I have uploaded a complete test using vagrant for someone to test. https://github.com/cdenneen/hiera_test Currently hiera output regardless of merge_behavior is showing as "deep" Currently puppet erb with hiera is showing as "native" regardless of merge_behavior setting This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.