Puppet 3.6 in EPEL7 is long EOL and has real security problems. As
discussed on devel@ (archive), it's not feasible to upgrade it within
EL7 so the intent is to retire it instead. Unless there are serious
reasons not to, I'll proceed with this in a week.
Ewoud Kohl van Wijngaarden
May 16, 2022 8:32:58 PM Maxwell G <gotmax(a)e.email>:
On Tuesday, April 19, 2022 3:14:56 PM CDT Kevin Fenzi wrote:
> In epel8 I will be converting the 'ansible' epel8 package into the
> upstream ansible-5 meta collections package (which also pulls in
I have rebased ansible to ansible 5 in epel8 and submitted a Bodhi update.
I would appreciate if you could help test the update and provide feedback. We
are also providing a newer version of ansible 5 in epel8-next that depends on
the newer version of ansible-core available in CentOS 8 Stream. Here is the
Bodhi update for the epel8-next version.
I also branched ansible for epel9 and epel9-next. Here[3,4] are the Bodhi
updates for that.
Remember that ansible 5 is just a bundle of ansible collections that are
released together, and it depends on ansible-core (the engine) which provides
the core modules, engine, and command line tools. This provides the
"batteries-included" approach that users of ansible classic (ansible 2.9.x and
below) are used to. If you prefer a more minimalist approach, you can install
ansible-core alongside the specific collections you need. You can install
collections through EPEL's ansible-collection-* RPM packages or from Ansible
Galaxy. If you would like to do this, you can switch to ansible-core with `dnf
swap ansible ansible-core`.
Maxwell G (@gotmax23)