Jira (HI-547) Unable to use 'nil' in backend to force default

[Sean Millichamp (JIRA)]

Title: Message Title

Sean Millichamp created an issue   Hiera / HI-547 Unable to use 'nil' in backend to force default Issue Type: Bug Affects Versions: HI 3.2.1 Assignee: Unassigned Created: 2016/12/13 10:50 AM Priority: Normal Reporter: Sean Millichamp In older versions of Hiera you could use a nil in the backend to force the Hiera default to be selected. For example, given the simple Hierarchy: --- :hierarchy: - 'data/host' - 'data/common' And data/common with: my_var: 'global val' You could use: my_var: ~ And Hiera would return the specified default value back to Puppet. This would allow the intentional "unsetting" of a particular key in Hiera for a small set of hosts that otherwise received more global Hiera-based settings. This used to work in Hiera and was usable from Puppet with hiera('my_key', 'a default') Now, Hiera (arguably more correctly) returns the found value nil, but Puppet doesn't fall back to the default, it instead raises an error and aborts the catalog compilation. This breaks a small but important bit of flexibility in Hiera. 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.