Forge Home


IUS repository management


9,494 latest version

5.0 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

  • 0.1.4 (latest)
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Jul 20th 2018
This version is compatible with:
  • Puppet Enterprise 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 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.8.0
  • , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'eyp-ius', '0.1.4'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eyp-ius
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eyp-ius --version 0.1.4

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.



eyp/ius — version 0.1.4 Jul 20th 2018


Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Development


setup Inline with Upstream Stable (IUS) repository

Module Description

This module enables the IUS repository for RHEL and CentOS 5/6/7


What ius affects

  • Manages a package called ius-release

Beginning with ius

Inlcude ius class to install ius repository

class { '::ius': }


We can also use this module to ensure IUS' absence:

class { '::ius':
  ensure => 'absent',



  • package_ensure: package status (default: 'installed')
  • import_gpgkey: automatically import IUS GPG key (default: true)
  • enable_repo_ius: controls enable flag (default: true)
  • enable_repo_ius_debug: controls enable flag (default: false)
  • enable_repo_ius_source: controls enable flag (default: false)
  • enable_repo_ius_dev: controls enable flag (default: false)
  • enable_repo_ius_dev_debug: controls enable flag (default: false)
  • enable_repo_ius_dev_source: controls enable flag (default: false)
  • enable_repo_ius_testing: controls enable flag (default: false)
  • enable_repo_ius_testing_debug: controls enable flag (default: false)
  • enable_repo_ius_testing_source: controls enable flag (default: false)


We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request