Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

rpmrepos

Setup 3rd party RPM repos
Project URLRSS FeedReport issues

11,450 downloads

11,450 latest version

2.1 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.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.0.1 (latest)
released Feb 11th 2013

Start using this module

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

Add this module to your Puppetfile:

mod 'metcalfc-rpmrepos', '0.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add metcalfc-rpmrepos
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install metcalfc-rpmrepos --version 0.0.1

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
Tags: centosrhelrpmepelrpmforge

Documentation

metcalfc/rpmrepos — version 0.0.1 Feb 11th 2013

History

Michael Stahnke wrote puppet-module-epel. Lee Boynton followed up with puppet-rpmforge which has a dependancy on puppet-module-epel for a fact and rpm key importing.

It seems like managing third party repos is a common task. If we're going to have a cross module dependancy we might as well merge the modules.

Why?

EPEL and RepoForge are two common third party RPM repositories. To parrot Michael Stahnke, "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."

There are also some packages which don't play nicely between the two (nagios-plugins comes to mind) and when possible that has been captured here.

Configure EPEL (Extra Repository for Enterprise Linux)

include rpmrepos::epel

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

You can enable them using class parameters (testing => true).

Proxy

If you have an http proxy required to access the internet, you can use the $proxy variable in the class parameters. If it is set to a value other than 'absent' a proxy will be setup with each repository. Note that otherwise each of the repos will fall back to settings in the /etc/yum.conf file.

Configure RepoForge

include rpmrepos::rpmforge

About

This module basically just mimics the rpmforge-release rpm. The same repos are enabled/disabled and the GPG key is imported. In the end you will end up with the RepoForge (aka RPMForge) repos configured.

The following Repos will be setup and enabled by default:

  • rpmforge

Other repositories that will setup but disabled (as per the rpmforge-release setup)

  • rpmforge-extras
  • rpmforge-testing

You can enable them using class parameters (testing => '1').

Proxy

If you have an http proxy required to access the internet, you can use the $proxy variable in the class parameters. If it is set to a value other than 'absent' a proxy will be setup with each repository. Note that otherwise each of the repos will fall back to settings in the /etc/yum.conf file.

Futher Information

Testing

  • This was tested using Puppet 2.7.x on Centos5/6 I assume it will work on any
  • RHEL variant Also, I think this should work with earlier versions of Puppet
  • (2.6.x at least)

License Apache Software License 2.0