remi

pdk
Configure the remi repository and import the GPG keys.

Okumura Takahiro

hfm

41,936 downloads

12,739 latest version

5.0 quality score

Version information

  • 1.11.0 (latest)
  • 1.10.0
  • 1.9.0
  • 1.8.0
  • 1.7.0
  • 1.6.0
  • 1.5.1
  • 1.5.0
  • 1.4.0
  • 1.3.2
  • 1.3.1
  • 1.3.0
  • 1.2.0
  • 1.1.6
  • 1.1.5
  • 1.1.4
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • 1.1.0
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
released Oct 17th 2018
This version is compatible with:
  • Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=3.0.0 < 6.0.0
  • RedHat
    ,
    CentOS
    ,
    Scientific

Start using this module

Documentation

hfm/remi — version 1.11.0 Oct 17th 2018

puppet-remi

Build Status Puppet Forge

Table of Contents

  1. Description
  2. Setup - The basics of getting started with remi
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Description

This module configure Remi's RPM repository and import RPM-GPG-KEY-remi.

Setup

Beginning with remi

To configure the remi with default parameters, declare the remi class.

include remi

Usage

Configuring remi

class { 'remi':
  remi_safe_enabled  => 1,
  remi_php71_enabled => 1,
}

Configuring modules from Hiera

---
remi::remi_safe_enabled: 1
remi::remi_php71_enabled: 1

Reference

Classes

Public Classes

  • remi: Configure the remi repository and import the GPG keys.

Private Classes

  • remi::rpm_gpg_key: Import the RPM GPG key for the Remi.

Parameters

remi

  • ensure: Whether the RPM-GPG-KEY-remi file should exist. Default to present.
  • path: The path to the RPM-GPG-KEY-remi file to manage. Must be an absolute path. Default to '/etc/pki/rpm-gpg/RPM-GPG-KEY-remi'.

Development

Running tests

The STNS puppet module contains tests for both rspec-puppet (unit tests) and beaker-rspec (acceptance tests) to verify functionality. For detailed information on using these tools, please see their respective documentation.

Testing quickstart

  • Unit tests:
$ bundle install
$ bundle exec rake lint
$ bundle exec rake validate
$ bundle exec rake spec
  • Acceptance tests:
# Set your DOCKER_HOST variable
$ eval "$(docker-machine env default)"

# Run beaker acceptance tests
$ BEAKER_set=centos7 bundle exec rake beaker