Forge Home


Manage the Puppet agent's noop configuration setting


7,106 latest version

4.5 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.1 (latest)
released Jan 2nd 2017
This version is compatible with:
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'joshs-agent_noop', '0.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add joshs-agent_noop
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install joshs-agent_noop --version 0.1.1

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.



joshs/agent_noop — version 0.1.1 Jan 2nd 2017


Table of Contents

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


Simple module to handle switching agents in and out of noop mode


What agent_noop affects

Sets noop parameter in puppet.conf based on the supplied parameter

Setup Requirements

Requires puppetlabs/inifile

Beginning with agent_noop


class { 'agent_noop':
  noop_mode => true,


Obviously the current agent run will continue in the noop mode it started in, the change will take effect on the next agent run.


Release Notes/Contributors/Etc.