-
Notifications
You must be signed in to change notification settings - Fork 135
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
Bump min version of stdlib #681
base: main
Are you sure you want to change the base?
Conversation
PR puppetlabs#637 uses stdlib::deferrable_epp that is only available in v8.4.0[1] [1] puppetlabs/puppetlabs-stdlib#1253 Change-Id: I455cec0ec1c6a2ec63b2ab0c19b2b7a2119f2f26
I'm not sure if that's the right move. I think instead we should move stdlib >= 9. https://github.com/puppetlabs/puppetlabs-kubernetes/blob/main/manifests/config/kubeadm.pp#L369-L370 for example still uses the deprecated merge() method: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/puppet/functions/merge.rb And that fails on puppet 8 with strict mode on. I think that metadata.json claims stdlib 9 + Puppet 8 compatibility isn't correct at the moment. The deprecated function calls should be removed and the stdlib lower version should be raised to 9. |
@bastelfreak I think bumping from |
I think raising the stdlib version always justifies a major releases. That's how we usually did it in the past. And when you bump the lower version to 8 I think you should lower the maximum version, so basically |
The lower stdlib version change should have been done in 9f9f0eb, that is part of However, if you would prepare |
I agree with @deric , think of this PR as fixing a bug in the lower constraint for stdlib I wonder if there's a good way to test for these kind of issues? |
Summary
PR #637 uses stdlib::deferrable_epp that is only available in v8.4.0[1]
[1] puppetlabs/puppetlabs-stdlib#1253
Checklist
puppet apply
)