It started in puppet 4, I believe 4.3. The lookup options go anywhere in
your hiera data, common.yaml or somewhere more specific. It will merge, so
you can add the ntp::servers key in common and sql2014::install_options in
a fqdn/role type tier if need be.
On Wednesday, January 27, 2016, Corey Osm
1. Can this be done in PE 3.8?
2. Its not clear where the lookup_options need to go. Does the
lookup_options go in hiera.yaml?
https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick.html#setting-lookupoptions-in-data
lookup_options: ntp::servers: merge: native? (I don't need deep me
Corey, take a look at the lookup_options to specify merge behavior with
APL. Prior to this, APL would not do hash lookups with any merge behavior.
This should change that:
https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick.html#specifying-merge-behavior
and
https://docs.puppetlabs.com
I have the following code which uses the auto binding feature to lookup a hiera
value. This is nothing new though. The problem I see is that there is no way
to tell puppet to use hiera_hash() for the install_options.
class sql2014(
Hash $install_options= {},
String $instance_name
