(MODULES-11115) add Rocky Linux 8 compatibility

[vchepkov]

No description provided.

[CLAassistant]

All committers have signed the CLA.

[puppet-community-rangefinder]

mysql::params is a class

Breaking changes to this file WILL impact these 2 modules (exact match):

• edestecd-mariadb
• brucem-ezpublish

Breaking changes to this file MAY impact these 1 modules (near match):

• willdurand-bazinga

This module is declared in 143 of 576 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[ghoneycutt]

Suggest adding this to the provision.yaml so acceptance testing shows this platform works.

[vchepkov]

I don't mind, just don't know how to find out what images are available.
Vagrant rockylinux/8 is there

[pmcmaw]

Hey @vchepkov

We would be more than happy to accept your PR (the code change) to make this module compatible with Rocky. However when adding to the metadata.json and provision.yaml it suggests that we would be supporting this OS which is something the team would not be able to do.

Note - I have updated your PR title to include compatibility rather than support.

[vchepkov]

@pmcmaw , would you like me to remove change to metadata.json? As long as module's manifest doesn't make any decision based on the metadata, it should be fine. Some modules do that, unfortunately, https://github.com/voxpupuli/puppet-yum/blob/master/manifests/init.pp#L108

[pmcmaw]

Yeah none of our supported modules do that. If you remove the metadata change and just have the manifest change I will get it merged. There was a fix merged earlier for spec test failures so if you rebase they will pass. 👍

[vchepkov]

@pmcmaw , done