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 YAML levels like this
# was impossible in the old format.
- name: "Exported JSON nodes"
data_hash: json_data
paths:
# Puppet checks these in order. Even though this is a single
# item in the hierarchy, it acts like multiple hierarchy levels.
- "nodes/%{trusted.certname}.json"
- "insecure_nodes/%{facts.fqdn}.json"
- name: "Virtualization platform"
path: "virtual/%{facts.virtual}.yaml"
- name: "Common defaults"
path: "common.yaml"
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 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 subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/cb2e7379-bece-4dcf-9f70-5f8aaaad3289%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
