agent_run_with_tags
Version information
This version is compatible with:
- Puppet Enterprise 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.7.0 < 7.0.0
- , , , , , , , ,
Tasks:
- agent_run_tags
Start using this module
Add this module to your Puppetfile:
mod 'martyewings-agent_run_with_tags', '1.0.0'Learn more about managing modules with a PuppetfileDocumentation
agent_run_with_tags
Table of Contents
- Description
- Setup - The basics of getting started with agent_run_with_tags
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Description
The Task in this module fills a hole in orchestrators native abilities. It allows you to run puppet agent with the --tags options on linux nodes running a bash shell.
By default it requires just one tag to be passed as an option, it allows up to 2. there are also 2 additional optional parameters param1 and param2 which can be used to pass standard puppet agent flags, such as --noop or --debug
Setup
Beginning with agent_run_with_tags
Install the module, the tasks will be populated in the tasks dropdown in the PE console
Usage
This task can be run against any linux node with a bash shell, it has 4 parameters:
tag1 - mandatory the tag you want to run the agent run with tag2 - an optional second tag param1 - an optional param that can be used to pass any agent flag, valid options include --debug --noop --fingerprint param2 - a second optional parameter incase one is not enough
Reference
Limitations
restricted to use on linux platforms with a bash shell
Development
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.