Allow some bacula::params::validate parameter values to be undef(ined)#10
Allow some bacula::params::validate parameter values to be undef(ined)#10mjhennig wants to merge 1 commit into
Conversation
|
The main reason these were left as That said, you are right. If the calling class uses |
|
Thank you! Note, however, that one may also consider leaving the empty string defaults but changing the conditional statements later on - as an alternative to this approach. Though I am not sure which way might be better. |
|
I'm running into this now, with puppet 4. Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, "" is not an absolute path. at /etc/puppet/environments/production/modules/bacula/manifests/params/validate.pp:183:5 on node puppet1 |
Use
undefas default value forbacula::params::validateparameters that are allowed to be (and even checked for being) undefined - rather than using an empty string (''), which seems to override any undefined parameters and thus causes validation to fail.