-
Notifications
You must be signed in to change notification settings - Fork 6
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
rspec-puppet-facts: Require 3.0.0 #125
Conversation
bf8e78d
to
2e9936a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're doing a breaking change, should we explicitly set facterdb_string_keys
to true in this release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good to verify this in some module(s)
55e75dd
to
7ff571c
Compare
test at voxpupuli/puppet-example#51 |
08cc2ae
to
5415037
Compare
Previously our tests didn't honour our spec/spec_helper.rb. This configures some rspec defaults for our Puppet modules. It makes sense that our tests use the same settings. This revealed some problems in other PRs: voxpupuli#125
I would like to release this as breaking change. That will require us to do a modulesync. That in turns ensures that we've a PR and a CI run for each module before we pull this change in.