Hello,
this work :
hiera -d -c /etc/puppetlabs/puppet/hiera.yaml core::packages
::environment=production ::osfamily=RedHat
this does not (at least on my platform) :
hiera -d -c /etc/puppetlabs/puppet/hiera.yaml core::packages
::environment=production ::os.family=RedHat
(note the dot between
Hi
I am in the process of migrating v3 hiera.yaml to v5 and I would like all
hash merges to merge 'deep' by default, the same way :merge_behavior:
deeper in v3 parameter provides.
I can't seem to find an easy way to do this after reading the docs - I
understand lookup_options: need to be se
On Fri, 27 Apr 2018, at 17:34, du wrote:
>
>
> Hi
>
> I am in the process of migrating v3 hiera.yaml to v5 and I would like all
> hash merges to merge 'deep' by default, the same way :merge_behavior:
> deeper in v3 parameter provides.
>
>
> I can't seem to find an easy way to do this after
On 27/04/18 17:34, du wrote:
Hi
I am in the process of migrating v3 hiera.yaml to v5 and I would like
all hash merges to merge 'deep' by default, the same way
:merge_behavior: deeper in v3 parameter provides.
I can't seem to find an easy way to do this after reading the docs - I
understand
On 27/04/18 18:12, Louis Coilliot wrote:
Hello,
this work :
hiera -d -c /etc/puppetlabs/puppet/hiera.yaml core::packages
::environment=production ::osfamily=RedHat
this does not (at least on my platform) :
hiera -d -c /etc/puppetlabs/puppet/hiera.yaml core::packages
::environment=producti
Hello Puppeteers,
Relearning Puppet (converting Ansible, Chef knowledge), not sure best
approach for this. How can I configure systems based on state of another
system? Essentially, I would use a tool like Terraform to bring up
systems. When their IP addresses are available, I would then us
