Forge Home


A Hiera 5 backend for Redis


5,342 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.2.0 (latest)
  • 0.1.1 (deleted)
  • 0.1.0 (deleted)
released Jul 23rd 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 >= 4.7.0 < 6.0.0
  • , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'andrewm3-hiera_redis', '0.2.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add andrewm3-hiera_redis
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install andrewm3-hiera_redis --version 0.2.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.



andrewm3/hiera_redis — version 0.2.0 Jul 23rd 2018


Table of Contents

  1. Description
  2. Setup - The basics of getting started with hiera_redis
  3. Usage - Configuration options and additional functionality
  4. Limitations - OS compatibility, etc.
  5. Development - Guide for contributing to the module


This module provides a Hiera 5 backend for Redis.


Setup Requirements

The backend requires the redis gem installed in the Puppet Server JRuby. It can be installed with:

/opt/puppetlabs/bin/puppetserver gem install redis

It is also recommended to install the gem into the agent's Ruby:

/opt/puppetlabs/puppet/bin/gem install redis

This allows commands such as puppet apply or puppet lookup to use the backend.

Beginning with hiera_redis

If Redis is running on the Puppet master with the default settings, specifying the lookup_key as 'redis_lookup_key' is sufficient, for example:

version: 5
  - name: hiera_redis
    lookup_key: redis_lookup_key


By default, the backend will query Redis with the key provided. It is also possible to query multiple scopes such as with the YAML backend, where the expected key in Redis is composed of the scope and the key separated by a character (default is :). For example, the following can be used:

version: 5
  - name: hiera_redis
    lookup_key: redis_lookup_key
        - osfamily/%{}
        - common

The backend then expects keys of a format such as common:foo::bar for a lookup of 'foo::bar'.

The other options available include:

  • host: The host that Redis is located on. Defaults to 'localhost'.
  • port: The port that Redis is running on. Defaults to 6379.
  • db: The database number to query on the Redis instance. Defaults to 0.
  • scope: The scope to use when querying the database.
  • scopes: An array of scopes to query. Cannot be used in conjunction with the scope option.
  • separator: The character separator between the scope and key being queried. Defaults to ':'.


This module has only been tested on CentOS.


PRs welcome.