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
- Puppet >= 5.0.0 < 7.0.0
- , , ,
Tasks:
- puppet_lookup
Start using this module
Add this module to your Puppetfile:
mod 'tkishel-puppet_lookup', '0.1.0'
Learn more about managing modules with a PuppetfileDocumentation
puppet_lookup task
Table of Contents
- Description
- Requirements
- Usage - Basic
- Reference - Parameters
- Limitations - Parameters Not Implemented
- Getting Help - With Tasks
Description
This module provides the puppet_lookup
task.
This task allows you to run puppet lookup
via the Console or the command line.
Requirements
This module is compatible with Puppet Enterprise.
Usage
Use the puppet task run
command, specifying the nodes and the key you want to retrieve:
puppet task run puppet_lookup --nodes master.example.com key=test
Note that the --nodes
parameter is limited to masters and compile masters.
For example, on the command line, run:
[root@pe-agent ~]# puppet task run puppet_lookup --nodes $(puppet config print server) key=puppet_enterprise::profile::master::java_args
Starting job ...
Note: The task will run only on permitted nodes.
New job ID: 1
Nodes: 1
Started on master.example.com ...
Finished on node master.example.com
status : success
command : puppet lookup puppet_enterprise::profile::master::java_args --node master.example.com --environment production --merge first --render-as json
results :
Xms : 3072m
Xmx : 3072m
Job completed. 1/1 nodes succeeded.
Duration: 2 sec
Reference
To view the available parameters for this task, on the command line, run:
puppet task show puppet_lookup
Limitations
The following puppet lookup
command parameters are not implemented:
--default
--facts
--knock-out-prefix
--type
Getting Help
To show help for tasks, run puppet task run --help
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.