This version is compatible with:
- Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.7.0 < 6.0.0
- , , , , , , ,
Start using this module
Add this module to your Puppetfile:
Learn more about managing modules with a Puppetfilemod 'beersy-hiera_lookup', '0.1.0'
Puppet Hiera Lookup Task
This module adds a Task for performing hiera lookups.
For Puppet Enterprise users, this means you can allow users or admins to perform hiera lookups without giving them SSH access to your Puppet master! The ability to run this task remotely or via the Console is gated and tracked by the RBAC system built in to PE.
This module is compatible with Puppet Enterprise and Puppet Bolt.
To run tasks with Puppet Enterprise, PE 2017.3 or later must be used.
To run tasks with Puppet Bolt, Bolt 0.5 or later must be installed on the machine from which you are running task commands. The master receiving the task must have SSH enabled.
Puppet Enterprise Tasks
With Puppet Enterprise 2017.3 or higher, you can run this task from the console or the command line.
Here's a command line example where we are looking up
ntp::servers from the Puppet master,
[abir@workstation]$ puppet task run hiera_lookup keys=ntp::servers -n master.corp.net Starting job ... New job ID: 346 Nodes: 1 Started on master.corp.net ... Finished on node master.corp.net STDOUT: key: ntp::servers --- - 0.us.pool.ntp.org - 1.us.pool.ntp.org - 2.us.pool.ntp.org - 3.us.pool.ntp.org ------------------------------------------- Job completed. 1/1 nodes succeeded. Duration: 10 sec
With Bolt, you can run this task on the command line like so:
bolt task run hiera_lookup keys=ntp::servers --nodes master.corp.net
keys: A comma-separated list of keys to look up
environment: Environment to use for look up (optional)
certname: Node to use for look up (optional)
explain: Enable explain (optional). Defaults to no.
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.