Version information
This version is compatible with:
- , ,
Start using this module
Add this module to your Puppetfile:
mod 'tag1-yumrepos', '0.9.5'
Learn more about managing modules with a PuppetfileDocumentation
yumrepos puppet modules
Yum repo definitions for enterprise linux (RHEL/CentOS) Each repo to manage is handled in its own class.
Currently includes repo definitions for the following yum repos (class names in parenthesis):
- Drupal Drush 7 (yumrepos::drush7)
- Drupal Drush 8 (yumrepos::drush8)
- Drupal Drush 9 (yumrepos::drush9)
- Elasticsearch 1.6 (yumrepos::elasticsearch16)
- ELRepo (yumrepos::elrepo)
- EPEL (yumrepos::epel)
- Grafana (yumrepos::grafana)
- IUS Community and optionally IUS Community Archive and Testing repos (yumrepos::ius)
- Jenkins (yumrepos::jenkins)
- Jpackage (yumrepos::jpackage)
- Logstash 1.4 (yumrepos::logstash14)
- MariaDB 10 (yumrepos::mariadb10)
- New Relic (yumrepos::newrelic)
- Nginx (yumrepos::nginx)
- Percona (yumrepos::percona)
- PHP XHProf for IUS PHP 5.6 (yumrepos::phpxhprof)
- Phusion Passenger (yumrepos::passenger)
- PuppetLabs (yumrepos::puppetlabs)
- Remi-safe (yumrepos::remi_safe)
- RepoForge (yumrepos::repoforge)
- Varnish 3 (yumrepos::varnish3)
- Varnish 4.0 (yumrepos::varnish4)
- Varnish 4.1 (yumrepos::varnish41)
- Varnish 4.1 modules (yumrepos::varnish_41_modules)
- Zabbix 2.4 (yumrepos::zabbix24)
Usage
"include yumrepos::ius"
or
"require => Class['yumrepos::ius']"
or
"class { 'yumrepos::ius': }"
Switching 'ius' with whichever repo you would like to enable for the host.
Optional Parameters
Additional configuration can be made through class parameters. Each yumrepos class accepts multiple parameters to override options such as URL, enabled, package includes/excludes, and enabling of gpg checks. Defaults are defined in params.pp.
Example:
class { 'yumrepos::epel':
epel_url => 'http://your.local.mirror.com/epel/',
epel_exclude => 'some packages to avoid',
epel_includepkgs => 'comma-separated packages to include',
}
Example Using Hiera
This example shows how you can configure the yumrepos classes using Hiera.
Hiera yaml configuration file (common, per-host, or whatever you have setup in your case):
yumrepos::epel::epel_url: 'http://your.local.mirror.com/epel/'
yumrepos::epel::epel_exclude: 'drupal*'
And then the class can be called from your puppet manifests without having to pass any of the parameters:
class { 'yumrepos::epel': }
General Information
RPM GPG keys are installed and enabled for repos where available.
Most settings are in parameters (defaults included via params.pp) so that things can be easily overridden from calling classes, Hiera, etc.
Requirements
Facter 1.7.0+ is required for our use of the operatingsystemmajrelease variable. This can be worked around with older puppet versions by defining a custom fact to strip the point release information from the operatingsystemrelease fact.
Copyright (c) 2014, Tag1 Consulting, Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.