Add strict_variables support when puppetdb is not on puppetmaster#126
Add strict_variables support when puppetdb is not on puppetmaster#126kbarber merged 4 commits intopuppetlabs:masterfrom
Conversation
|
@mcanevet can you give a greater description of what you are trying to solve here? |
|
@kbarber sure. Is it clear enough with this description ? |
|
@mcanevet maybe we should just change our rspec-puppet/travis setup to always have this 'strict_variables' option on for 3.5.0? That way we won't regress in the future. |
|
@kbarber and now everything fails :-) |
|
@kbarber last failing unit test is due to bugs in puppetlabs-postgresql. I'm fixing it here: puppetlabs/puppetlabs-postgresql#402 |
|
@mcanevet we specialize in opening cans of worms it seems :-). |
|
@kbarber I added |
|
@mcanevet I'd rather not allow this to go in without fixing the upstream confirmed, otherwise no one will find the time to fix it correctly :-). Also - I'd rather this be a mandatory pass/fail if we can. I've had @apenney merge in your change to postgresql, but I'm still seeing an error related to postgres when I re-run your tests. Can you take another look please? https://travis-ci.org/puppetlabs/puppetlabs-puppetdb/jobs/22608476 |
|
@mcanevet actually looks like its turtles all the way down. Its throwing an error for 'concat' now, not postgresql. |
|
@kbarber fixed |
|
@mcanevet excellent. I think the last thing is to remove the allow_failures part. I'm more of the preference to fail hard now we've got it right. |
|
@kbarber done |
Add strict_variables support when puppetdb is not on puppetmaster
|
@mcanevet thanks mate, 2 modules down, god knows how many to go. You've been great on this one, thanks very very much. |

When using the new
strict_variablesfeature of puppet 3.5, includingpuppetdb::master::configon the puppetmaster fails withUndefined variable "puppetdb::disable_ssl"becauseClass[puppetdb]is not declared and sopuppetdb::disable_sslis not defined if puppetdb and puppetmaster are not on the same machine.