-
Notifications
You must be signed in to change notification settings - Fork 203
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 on puppet 6.17 breaks due to removal of default_env #796
Comments
Same on puppet 5.5.21 |
|
+1 same problem here |
Got a quick fix for this up in a PR that hopefully someone from the maintainers can validate and/or improve since this is my first time dabbling in this repo: #797 |
There were upstream issues with broken dependencies that we upstreamed a fix for and because of this we needed to pin to latest (unreleased) version of `rspec-puppet` gem. In the process, it seems like we also discovered that our fork was not required as the tests all pass so it was likely that we just had a fork to have a pre-release features ready which are now in mainline. Upstream bug: rodjek/rspec-puppet#796 Upstream fix: rodjek/rspec-puppet#797
Since this is now changed to `DEFAULT_ENV`, we now create the old function alias to retain functionality. Bug: #796 Upstream: https://github.com/puppetlabs/puppet/blob/94df3c1a3992d89b2d7d5db8a70373c135bdd86b/lib/puppet/util.rb
@dlucredativ I don't know enough about this gem to answer that - the fix is independent of the base version though |
Ok it seems that you only created 73fbbe2 and @scotje cherry-picked it into b6807eb. I just don't know why. |
2.7.9 unintentionally included commits intended for 2.8.x (or 3.x) as they break some peoples existing tests. We yanked the 2.7.9 release and released 2.7.10 which is just 2.7.8 plus only the fix for |
It looks like default_env was removed in puppet 6.17 - specifically in this commit:
puppetlabs/puppet@94df3c1
This results in an exceptiion similar to the following when rspec tries to run tests:
Not sure about what way to go about fixing this.
The text was updated successfully, but these errors were encountered: