This module basically just mimics the epel-release rpm. The same repos are enabled/disabled and the GPG key is imported. In the end you will end up with the EPEL repos configured.
The following Repos will be setup and enabled by default:
- epel
Other repositories that will setup but disabled (as per the epel-release setup)
- epel-debuginfo
- epel-source
- epel-testing
- epel-testing-debuginfo
- epel-testing-source
In nearly all cases, you can simply include epel or classify your nodes with the epel class. There are quite a few parameters available if you need to modify the default settings for the epel repository such as having your own mirror, an http proxy, or disable gpg checking.
A list of all parameters is available in REFERENCE.md.
You can also use a puppet one-liner to get epel onto a system.
puppet apply -e 'include epel'
If you have a http proxy required to access the internet, you can use either a class parameter in the epel class (epel_proxy), or edit the $proxy variable in the params.pp file. By default no proxy is assumed.
I am a big fan of EPEL. I actually was one of the people who helped get it going. I am also the owner of the epel-release package, so in general this module should stay fairly up to date with the official upstream package.
I just got sick of coding Puppet modules and basically having an assumption that EPEL was setup or installed. I can now depend on this module instead.
I realize it is fairly trivial to get EPEL setup. Every now-and-then however the path to epel-release changes because something changes in the package (mass rebuild, rpm build macros updates, etc). This module will bypass the changing URL and just setup the package mirrors.
This does mean that if you are looking for RPM macros that are normally included with EPEL release, this will not have them.
- This module is tested on CentOS 7 and 8 with Puppet 6 and Puppet 7.
- It should work on any RHEL variant such as RedHat, OracleLinux, Scientific Linux etc.
- Amazon Linux compatability is not promised, as EPEL doesn't always work with it.
- Support for EL5 and EL6 is deprecated. It may still work but we have no acceptance tests.
Install the necessary gems
bundle install --path vendor --without system_tests
Run the RSpec and puppet-lint tests
bundle exec rake test
If you have Vagrant >=1.1.0 you can also run system tests:
RSPEC_SET=centos-64-x64 bundle exec rake spec:system
Available RSPEC_SET options are in .nodeset.yml
This module is distributed under the Apache License 2.0. Since version 3, it is maintained by Vox Pupuli.
- Aaron [email protected]
- Alex Harvey [email protected]
- Chad Metcalf [email protected]
- Ewoud Kohl van Wijngaarden [email protected]
- Jeffrey Clark [email protected]
- Joseph Swick [email protected]
- Matthaus Owens [email protected]
- Michael Hanselmann [email protected]
- Michael Stahnke [email protected]
- Michael Stahnke [email protected]
- Michael Stahnke [email protected]
- Michael Stahnke [email protected]
- Mickaël Canévet [email protected]
- Nick Le Mouton [email protected]
- Pro Cabales [email protected]
- Proletaryo Cabales [email protected]
- Riccardo Calixte [email protected]
- Robert Story rstory@localhost
- Rob Nelson [email protected]
- Siebrand Mazeland [email protected]
- Stefan Goethals [email protected]
- Tim Rupp [email protected]
- Toni Schmidbauer [email protected]
- Trey Dockendorf [email protected]
- Troy Bollinger [email protected]
- Vlastimil Holer [email protected]
If you're on CentOS 7 or CentOS 8, you can just yum install epel-release as it's in centos-extras.