Skip to content
New issue

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

Add strict_variables support when puppetdb is not on puppetmaster #126

Merged
merged 4 commits into from
Apr 10, 2014

Conversation

mcanevet
Copy link
Contributor

@mcanevet mcanevet commented Apr 8, 2014

When using the new strict_variables feature of puppet 3.5, including puppetdb::master::config on the puppetmaster fails with Undefined variable "puppetdb::disable_ssl" because Class[puppetdb] is not declared and so puppetdb::disable_ssl is not defined if puppetdb and puppetmaster are not on the same machine.

@kbarber
Copy link
Contributor

kbarber commented Apr 8, 2014

@mcanevet can you give a greater description of what you are trying to solve here?

@mcanevet
Copy link
Contributor Author

mcanevet commented Apr 8, 2014

@kbarber sure. Is it clear enough with this description ?

@kbarber
Copy link
Contributor

kbarber commented Apr 8, 2014

@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.

@mcanevet
Copy link
Contributor Author

mcanevet commented Apr 8, 2014

@kbarber and now everything fails :-)

@mcanevet
Copy link
Contributor Author

mcanevet commented Apr 8, 2014

@kbarber last failing unit test is due to bugs in puppetlabs-postgresql. I'm fixing it here: puppetlabs/puppetlabs-postgresql#402

@kbarber
Copy link
Contributor

kbarber commented Apr 8, 2014

@mcanevet we specialize in opening cans of worms it seems :-).

@raphink
Copy link

raphink commented Apr 9, 2014

@mcanevet
Copy link
Contributor Author

mcanevet commented Apr 9, 2014

@kbarber I added env: PUPPET_GEM_VERSION="~> 3.5.0.rc3" STRICT_VARIABLES="yes"as allowed failure because the issue comes from puppetlabs-postgresql.
Can you merge this ?

@kbarber
Copy link
Contributor

kbarber commented Apr 9, 2014

@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

@kbarber
Copy link
Contributor

kbarber commented Apr 9, 2014

@mcanevet actually looks like its turtles all the way down. Its throwing an error for 'concat' now, not postgresql.

@mcanevet
Copy link
Contributor Author

@kbarber fixed

@kbarber
Copy link
Contributor

kbarber commented Apr 10, 2014

@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.

@mcanevet
Copy link
Contributor Author

@kbarber done

kbarber added a commit that referenced this pull request Apr 10, 2014
Add strict_variables support when puppetdb is not on puppetmaster
@kbarber kbarber merged commit 23849e4 into puppetlabs:master Apr 10, 2014
@kbarber
Copy link
Contributor

kbarber commented Apr 10, 2014

@mcanevet thanks mate, 2 modules down, god knows how many to go. You've been great on this one, thanks very very much.

@mcanevet mcanevet deleted the fix/strict_variables branch April 10, 2014 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants