We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We use boolean custom variables in our configuration. They work fine if they are true but they never end up in the configuration file if set to false.
true
false
false variables should be appear in the generated configuration.
false variables are ignored. Only true values and non-booleans are used.
I think the changes in 1ab1c6f are responsible for the bug. The if value conditions evaluate to false so the custom variables are ignored.
if value
icinga2::object::service { 'icinga2': ensure => present, import => [ 'generic-service', ], target => '/etc/icinga2/zones.d/globals.d/services.conf', display_name => 'Icinga2 Status', check_interval => '1m', retry_interval => '30s', check_command => 'icinga', zone => 'master', command_endpoint => 'host.name', apply => true, assign => [ 'host.vars.check.icinga2.enable == true' ], enable_active_checks => false, vars => { enable_active_checks => false, bla => false, foobar => true, } }
apply Service "icinga2" to Host { import "generic-service" display_name = "Icinga2 Status" check_command = "icinga" check_interval = 1m retry_interval = 30s enable_active_checks = false zone = "master" command_endpoint = host.name vars.foobar = true assign where host.vars.check.icinga2.enable == true }
puppet module list
puppet -V
The text was updated successfully, but these errors were encountered:
ed7affe
Merge pull request #406 from Icinga/bug/Boolean-false-does-not-appear…
daedfba
…-in-config-400 fix #400 boolean false custom variables do not appear in configuration
fix voxpupuli#400 boolean false custom variables do not appear in con…
522aeb2
…figuration
lbetz
No branches or pull requests
We use boolean custom variables in our configuration. They work fine if they are
true
but they never end up in the configuration file if set tofalse
.Expected Behavior
false
variables should be appear in the generated configuration.Current Behavior
false
variables are ignored. Onlytrue
values and non-booleans are used.Possible Solution
I think the changes in 1ab1c6f are responsible for the bug. The
if value
conditions evaluate tofalse
so the custom variables are ignored.Steps to Reproduce (for bugs)
true
variables are included.Your Environment
puppet module list
): We are using a fork of the module but it contains the same utils.rb as the latest upstream version.puppet -V
): 4.10.1The text was updated successfully, but these errors were encountered: