Affects Version/s: PUP 3.7.2
Fix Version/s: None
puppetmaster runs on:
[root@puppetmaster2dev ~]# cat /etc/redhat-release
CentOS release 6.2 (Final)
[root@puppetmaster2dev ~]# rpm -qa | egrep '^(puppet|hiera)'
Assuming this class:
And having a yaml null in my hieradata, or a key with no value, like either of these:
I get errors about how the class needs a parameter.
With an explicitly empty string I do not see this error, the class parameter is accepted.
The problem is that the class doesn't pick up how I've defined the hiera key "testing::cwood1::param1". Nevertheless the key is there and I am passing something, even if I am passing a representation of nothing.
I expected that this might have the same result as doing "$param1 = undef" since the undef there is the closest thing in puppet to ruby nil, yaml null. That said, there are a number of interesting tickets about true/truthy/false/nil handling and I will link those here since it's probably a subset of those issues.
Further, a straight command-line hiera lookup appears to represent these as nil.
A quick yaml read picks these up as nil, as well.