Forge Home

set_noop

Task to manipulate the 'noop' setting in an agent's puppet.conf.

10,494 downloads

7,591 latest version

4.9 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.1.6 (latest)
  • 1.1.5
  • 1.1.4
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • 1.1.0
  • 1.0.0
released Jul 9th 2019
This version is compatible with:
  • Puppet Enterprise 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 >= 4.0.0
  • , , , , , , , ,
Tasks:
  • set_noop

Start using this module

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

Add this module to your Puppetfile:

mod 'gabe-set_noop', '1.1.6'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add gabe-set_noop
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install gabe-set_noop --version 1.1.6

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.

Download

Documentation

gabe/set_noop — version 1.1.6 Jul 9th 2019

set_noop

This cross-platform module consists of a task to manipulate the "noop" setting in an agent's puppet.conf.

Task

The set_noop task updates an agent's puppet.conf to manipulate the "noop" setting in the [agent] section. For example, provided you've got SSH keys, host keys, bolt in your command path, and this module installed into your modulepath, setting nodes to noop mode is as simple as:

bolt task run set_noop setting=true \
  --nodes ssh://bert,ssh://ernie

For more information on Bolt's configuration and command-line options, refer to the Bolt online documentation.

Here's a more thorough example of taking some Linux nodes out of noop mode, prompting for the root user's password and ignoring SSH host key checks:

bolt task run set_noop setting=false \
  --no-host-key-check --user root --password \
  --nodes ssh://waldorf,ssh://statler

Similarly, a thorough example of setting Windows nodes into noop mode, logging in as Administrator, prompting for password, and using a non-ssl transport:

bolt task run set_noop setting=true \
  --no-ssl --user Administrator --password \
  --nodes winrm://kermit

This task will also become available in the Puppet Enterprise console, as soon as you install the module into your production environment. (Add it to your Puppetfile.)