-
Notifications
You must be signed in to change notification settings - Fork 228
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
Drop Puppet 5 support #791
Conversation
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.
I think dropping Puppet 5 should also drop all code. That's a much bigger patch.
If you're going to remove code, maybe just remove it for the puppetserver side of the module, but leave the agent code alone? After a lot of work, I've just upgraded by server infra to Puppet 6/Foreman 2. Most agents are Linux and are still on Puppet 4, (which I'll be upgrading to 6 in the next few weeks), but I've also got some Solaris 10 and 11 with Puppet 3 agents. 😢 |
We can just leave this be for now, it was inspired by dropping the support across our modules since their largest use case is through the foreman-installer and cleaning up code paths and test matrices. Also, we had a few modules starting to need Puppet 6+ features (e.g. EL8 module support). |
@alexjfisher how far along are you? I'd like to reconsider this because by now Puppet 5 AIO packages are no longer on yum.puppet.com so we no longer really test it. |
I've merged #822. |
No description provided.