jerakia-puppet
Summary
This gem provides the legacy data binding libraries and Hiera 3 backends for Puppet to lookup data via Jerakia directly using Ruby bindings or over the Jerakia Server REST API using the Jerakia client library
Puppet 4.9+ users
If you are using Puppet 4.9+ then you should use the Hiera 5 data provider that ships in the Jerakia Puppet Module to integrate Jerakia with Puppet. These libraries are intended to support older installations and will eventually be deprecated.
Installation
# /opt/puppetlabs/puppet/bin/gem install jerakia-puppet
# /opt/puppetlabs/bin/puppetserver gem install jerakia-puppet
Integrating Jerakia with Puppet
Introduction
There are numerous integration points between Jerakia and Puppet and it's not always clear exactly what method you should use. The reason for this is primarily that Puppet themselves are going through somewhat of a state of transition when it comes to data lookups, with the arrival of Hiera 5 in Puppet 4.9 and the planned deprecation of older legacy data lookup integration points such as the data_binding_terminus and the eventual deprecation of the current implementation of Hiera in future releases. These changes are happening over a long period of time to allow for users to sucessfully migrate, so in turn that means that Jerakia needs to be able to support the older (and still valid) ways of integrating external data providers and the newer methods being introduced in Puppet 4.9.
Below is a summary of the ways to integrate Jerakia with Hiera.
Users of Hiera 3 / Puppet < 4.9
Data binding terminus
A data_binding_terminus is ruby code that is called directly from Puppet and is used to pass lookups. It is configured with the data_binding_terminus in puppet.conf. Historically most users have only used none or hiera for this option.
Native binding
Jerakia ships with a terminus called jerakia that is a drop-in replacement for the current hiera one and can be enabled by configuring the following in puppet.conf
[main]
data_binding_terminus = jerakiaIn order for this terminus to work, the Jerakia ruby libraries must be loadable from Puppet. If you have installed Jerakia from the AIO system packages, you will need to also add the gem to Puppets' ruby in order to use this implementation.
REST Client binding (experimental)
If you have installed Jerakia 1.2+ from the AIO system package, and do not want to also maintain a separate copy of Jerakia core as a rubygem in Puppet, or if you wish to run Puppet and Jerakia on separate servers, there is a new (currently experimental) data binding terminus called jerakiaserver that ships in an external rubygem, jerakia-puppet, that uses the jerakia-client ruby libraries to integrate with Jerakia Server over HTTP REST.
In order to use this terminus, the puppet-databinding-jerakiaserver rubygem must be loadable from Puppets' Ruby
It can be configured in puppet.conf with
data_binding_terminus = jerakiaserverNote that the data_binding_terminus feature of Puppet is being deprecated and is expected to be removed in Puppet 6.0
Hiera 3.x backend
Jerakia ships with a Hiera 3.x backend that loads Jerakia directly and passes lookup requests. It has slightly slower performance than using the data binding terminus but otherwise operates transparently. To enable the Jerakia Hiera backend you need to have the Jerakia gem loadable from Puppets' ruby path. It can be configured simply with;
---
:backends:
- jerakiaOptional configuration can be given as a hash named :jerakia....
:jerakia:
:config: /etc/puppetlabs/code/jerakia.yamlSee configuring jerakia for acceptable configuration parameters.
Users of Puppet 4.9+ / Hiera 5
Puppet Data Function
From Puppet 4.9 the recommended integration method will be using the new data provider function that ships with the Jerakia Puppet Module. It is intended that this eventually becomes the only point of integration between Jerakia and Puppet, although the other integrations will still be included for the forseeable future.
See also
License
Jerakia libraries are distributed under the Apache 2.0 license