This but only applied to the hiera data bindings afaik, not to hiera
function calls.
On 6 June 2013 03:41, Ti Leggett shin...@gmail.com wrote:
Hm, that bug says it was a duplicate of 17474 and 17474 was revolved in
3.2.0-rc1. Do I have a variant of the bug that's still residual?
On Jun 5,
Responses inline.
On Jun 7, 2013, at 10:37 PM, Dan White y...@comcast.net wrote:
A couple of things:
$parameters is supposed to end up as a hash, right ?
You are setting a default value of an empty array !
$parameters = hiera('java', []),
Try changing ‘java’ to something it will
Here's what comes back from that.
Info: Applying configuration version '1370635086'
Notice: /Stage[main]/Java::Install/Notify[enable_v7]/message: current_value
absent, should be Key (noop)
Notice: /Stage[main]/Java::Install/Notify[enable_v6]/message: current_value
absent, should be Key (noop)
A couple of things:
$parameters is supposed to end up as a hash, right ?
You are setting a default value of an empty array !
$parameters = hiera('java', []),
Try changing ‘java’ to something it will not find and see the errors you get.
That is how I discovered it.
My additional code
Hm, that bug says it was a duplicate of 17474 and 17474 was revolved in
3.2.0-rc1. Do I have a variant of the bug that's still residual?
On Jun 5, 2013, at 7:12 PM, Dan White y...@comcast.net wrote:
http://projects.puppetlabs.com/issues/17105
Hiera booleans are broken -- explicit false value
It seems puppet thinks that variables evaluate to true even when they are
explicitly set to false in hiera YAML.
In my searching it seems like this should be fixed but with hiera 1.2.1 and
puppet 3.2.1 I'm still seeing this.
In my YAML I have:
# Java directives
java :
enable_jdk : false #
http://projects.puppetlabs.com/issues/17105
Hiera booleans are broken -- explicit false value registers as lookup failure
On Jun 5, 2013, at 4:52 PM, Ti Leggett wrote:
It seems puppet thinks that variables evaluate to true even when they are
explicitly set to false in hiera YAML.
In my
