Upgrade dependency, Ubuntu and Puppet version ranges #769
+7
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Upgrades upper limit of various version ranges in
metadata.json:Motivation
Being held back in what puppet modules we can use because of the version ranges in this module.
Additional Notes
Until #735 is resolved several of these higher versions are unattainable because
puppetlabs-rubyis holding backstdlibto < 7Describe your test plan
I would test with PDK but I couldn't because the PDK version set in this project is very old. I presume this is to maintain compatibility with Puppet v4.