Forge Home


Resource types for managing puppet master and agent


18,444 latest version

1.6 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

  • 1.4.0 (latest)
  • 1.3.1
  • 1.3.0
  • 1.2.0
  • 1.1.0
  • 1.0.0
  • 0.0.23
  • 0.0.22
  • 0.0.21
  • 0.0.20
  • 0.0.19
  • 0.0.18
  • 0.0.17
  • 0.0.16
  • 0.0.15
  • 0.0.14
  • 0.0.13
  • 0.0.12
  • 0.0.11
  • 0.0.10
  • 0.0.9
  • 0.0.8
  • 0.0.7
  • 0.0.6
  • 0.0.5
  • 0.0.4
  • 0.0.3
released Jan 15th 2016
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet 3.x
  • , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'stephenrjohnson-puppet', '1.4.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add stephenrjohnson-puppet
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install stephenrjohnson-puppet --version 1.4.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.



stephenrjohnson/puppet — version 1.4.0 Jan 15th 2016

Build Status

Puppet module

This module provides classes for managing the puppet agent and puppet master. It will setup passenger and apache on the puppetmaster. Please note this will not setup puppetdb. This can be configured using the puppetdb module Storedconfigs with puppetdb will only work on puppet versions newer than 2.7.12.


If you are using a RedHat based OS you also need to have the EPEL repo configured as this module requires the passenger apache module.

Requires the following modules from puppetforge: stdlib, apache, concat, inifile

Usage Note

If you are using this module to install a puppetmaster and serving the manifest of the machine. You may have issues with it halting the puppet master if it is running through webrick. In which case run a single puppet run using

puppet apply -e "class{'puppet::repo::puppetlabs': } Class['puppet::repo::puppetlabs'] -> Package <| |> class { 'puppetdb': }  class { 'puppet::master': storeconfigs => true }"


class { 'puppetdb': }
class { 'puppet::master':
    storeconfigs              => true,

Puppet Environments

Puppet 3.5 introduced a new way of handling Puppet environments known as Directory Environments. This is expected to become the default configuration as of Puppet 4.0, this module supports both methods.

Config Method (default)

class { 'puppet::master': }

puppet::masterenv {'dev':
    modulepath => '/etc/puppet/env/dev/modules',
    manifest   => '/etc/puppet/env/dev/site.pp',
puppet::masterenv {'production':
    modulepath => '/etc/puppet/env/production/modules',
    manifest   => '/etc/puppet/env/production/site.pp',

Directory method using environmentpath

class { 'puppet::master':
  environments => 'directory',

Optionally, an environmentpath parameter can be supplied to configure the base root of Puppet environments, this defaults to $confdir/environments


class { 'puppet::agent':
    puppet_server             => master.puppetlabs.vm,
    environment               => production,
    splay                     => true,

Deprecation Warning

The templatedir parameter will default to undef and will remove the setting from the puppet.conf file in version 2.0.0 of this module.


Install gems:

bundle install --path vendor/bundle

Lint and rspec-puppet:

bundle exec rake lint
bundle exec rake spec

If you have a working Vagrant setup you can run the rspec-system tests:

bundle exec rake beaker

To use different base boxes than the default pass the name of the box to the rake command with the BEAKER_set environment variable (check out .nodelist.yml for box names):

BEAKER_set=ubuntu-server-1404-x64 bundle exec rake beaker