Issue #17105 has been updated by Corey Hinshaw.
This behavior is still present in version 3.1.0. A workaround has been to use comment #1 above and explicitly call hiera() for lookups that should return a boolean value. However, it would be great if automatic hiera lookups had working support for booleans! ---------------------------------------- Bug #17105: Hiera booleans are broken -- explicit false value registers as lookup failure https://projects.puppetlabs.com/issues/17105#change-84480 Author: Nick Fagerlund Status: Needs Decision Priority: Normal Assignee: eric sorenson Category: databinding Target version: 3.x Affected Puppet version: 3.0.1 Keywords: Branch: `/var/lib/hiera/common.yaml:` --- ntp::disabled: false `fake_classes.pp:` class ntp ($disabled) { } include ntp This explodes! Although a `hiera ntp::disabled` call from the command line returns the correct result, Puppet registers this as a failed lookup and bails compilation with `Error: Must pass disabled to Class[Ntp]`. This doesn't happen with `true`, just `false`. I assume we're just doing an `if returned_value` or something somewhere, which will fail on both `nil` (value not found) and `false` (explicit false value found). We can't do that -- booleans are a core data type and Puppet should definitely accept them from Hiera. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
