Jira (HI-304) Override does not work with interpolation

[Michael Smith (JIRA)]

Title: Message Title

Michael Smith commented on HI-304   Re: Override does not work with interpolation Here's an example showing the buggy behavior: 1. Create a hiera.yaml config that specifies hiera.yaml --- :backends: - yaml :hierarchy: - common - alternate :yaml: :datadir: "/tmp/hieradata" 2. Create data sources at /tmp/hieradata /tmp/hieradata/common.yaml foo: '%{hiera("bar")}' bar: 'common' /tmp/hieradata/alternate.yaml bar: 'alternate' 3. Run hiera -c hiera.yaml foo and you'll see common printed. This is the expected behavior. Now to see the bug, swap common and alternate in hiera.yaml, so they're interpreted in a different order. We're going to use the order_override option to Hiera#lookup to restore the original order, but the output will differ from what we just saw in step 3 above. irb require 'hiera' hiera = Hiera.new(:config => 'hiera.yaml') hiera.lookup('foo', nil, {}, 'common') The result before this change shows alternate. The expected result is common, as above, and with the PR merged that's the behavior we get. Add Comment   This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.