Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

epel

Setup the EPEL package repo
Project URLRSS FeedReport issues

2,260 downloads

2,260 latest version

3.8 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 2.0.0 (latest)
released Jan 16th 2020
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 3.0.0 < 7.0.0
  • , , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'yakatz-epel', '2.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add yakatz-epel
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install yakatz-epel --version 2.0.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

yakatz/epel — version 2.0.0 Jan 16th 2020

Configure EPEL (Extra Repository for Enterprise Linux)

This module if forked from https://github.com/stahnma/puppet-module-epel in order to release support for RHEL 8.

About

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

Usage

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.

You can also use a puppet one-liner to get epel onto a system.

puppet apply -e 'include epel'

Proxy

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.

Why?

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.

Further Information

ChangeLog

=======

1.3.1

  • Remove an Epel::Rpm_gpg_key collector that could cause circular dependencies

1.3.0

  • Add ability to disable and not define any resources from this module. This is useful if another module pulls in this module, but you already have epel managed another way.

  • Ability to specify your own TLS certs

  • repo files are now templated instead of sourced.

  • properly use metalink vs mirrorlist

    1.2.2

  • Add dep on stdlib for getvar function call

    1.2.1

  • Minor fix that lets facter 1.6 still work

  • Enforce strict variables

    1.2.0

  • Rework testing to use TravisCI

  • If you specify a baseurl, disable mirrorlist

    1.1.1

  • Ensure that GPG keys are using short IDs (issue #33)

    1.1.0

  • Default URLs to be https

  • Add ability to include/exclude packages

    1.0.2

  • Update README with usage section.

  • Fix regression when os_maj_version fact was required

  • Ready for 1.0 - replace Modulefile with metadata.json

  • Replace os_maj_version custom fact with operatingsystemmajrelease

  • Works for EPEL7 now as well.

Testing

  • This is commonly used on Puppet Enterprise 3.x
  • This was tested using Puppet 3.3.0 on Centos5/6
  • This was tested using Puppet 6.10.1 on CentOS 8
  • This was tested using Puppet 3.1.1 on Amazon's AWS Linux
  • This was tested using Puppet 3.8 and Puppet 4 now as well!
  • Note Ruby 2.2 and Puppet 3.8 are not yet friends.
  • I assume it will work on any RHEL variant (Amazon Linux is debatable as a variant)
  • Amazon Linux compatability not promised, as EPEL doesn't always work with it.

Lifecycle

  • No functionality has been introduced that should break Puppet 2.6 or 2.7, but I am no longer testing these versions of Puppet as they are end-of-lifed from Puppet Labs.
  • This also assumes a facter of greater than 1.7.0 -- at least from a testing perspective.
  • I'm not actively fixing bugs for anything in facter < 2 or puppet < 3.8

Unit tests

Install the necessary gems

bundle install --path vendor --without system_tests

Run the RSpec and puppet-lint tests

bundle exec rake test

System tests

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

License

Apache Software License 2.0

Author/Contributors

Alternatives

If you're on CentOS 7 or CentOS 8, you can just yum install epel-release as it's in centos-extras.