Hey, it looks like everyone found this, but I wanted to add that we updated
this document with the hiera.yaml v5 format late last week, so if you were
looking for it outside of the google doc, it's up and running.
Being that I have followed the default structure this time the following
worked fine for me direct from the above link -
---
version: 5
defaults:
datadir: data
data_hash: yaml_data
hierarchy:
- name: "Nodes"
path: "nodes/%{trusted.certname}.yaml"
# Putting a JSON level between
I found that although that fixed my error, I got no data.
Turns out this is because you need a hiera.yaml in each environment folder
with the datadir specified to that environment (if you are using a
hieradata folder specific to each environment.
I also needed to change puppet.conf and add
The spec appears to be here -
https://docs.puppet.com/puppet/4.9/lookup_quick.html
On Wednesday, February 8, 2017 at 8:37:32 AM UTC+13, Joshua Schaeffer wrote:
>
> Okay I see that they are actually preparing to release Puppet 4.9.2 which
> is supposed to fix these issues. Does this mean they
Okay I see that they are actually preparing to release Puppet 4.9.2 which
is supposed to fix these issues. Does this mean they will release a new
puppet-agent package part of the PC1? Where can I go to track the progress
of this minor release?
>
--
You received this message because you are
So going through the ticket it looks like I should be putting "version: 5"
in the YAML file and that keys are not prefixed with a colon. But I get
errors when I make changes to my hiera.yaml file:
---
version: 5
backends: yaml
hierarchy:
- "fqdn/%{facts.fqdn}"
- "os/%{facts.osfamily}"
-
So going through the ticket it looks like you should be putting "version:
5" in the YAML file and that keys are not not prefixed with a colon. But I
get errors when I make changes to my hiera.yaml file:
---
version: 5
backends: yaml
hierarchy:
- "fqdn/%{facts.fqdn}"
- "os/%{facts.osfamily}"
