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
- , , , , , , , ,
This cross-platform module consists of a task to manipulate the "noop" setting in an agent's puppet.conf.
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.)
What are tasks?
Modules can contain tasks that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.