-
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
require PSH 5.x, require puppet-strings #84
Conversation
tested that at voxpupuli/puppet-yum#297 |
Codecov ReportBase: 1.63% // Head: 1.63% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #84 +/- ##
======================================
Coverage 1.63% 1.63%
======================================
Files 2 2
Lines 61 61
======================================
Hits 1 1
Misses 60 60 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Also contains #85 |
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.
This looks reasonable to me. I'm not thrilled about functions in the Gemfile but the alternative is probably worse.
This now uses a similar setup as puppet-syntax. Sideeffect is that for Puppet 6 tests, we pull in the 6.29 version or newer, which has a fix to pin to concurrent-ruby 1.1 and older.
with the release of puppetlabs_spec_helper 5, it can validate the REFERENCE.md. It won't pull in puppet-strings automatically, so the dependency needs to be added. The `strings:validate:reference` task is called within `validate`.
with the release of puppetlabs_spec_helper 5, it can validate the REFERENCE.md. It won't pull in puppet-strings automatically, so the dependency needs to be added. The
strings:validate:reference
task is called withinvalidate
.