[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
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}"
- common
yaml: datadir: /etc/puppetlabs/code/environments/%{::environment}/hieradata
Here are the errors I get:
root@fenix:/etc/puppetlabs/code/environments/sandbox# puppet apply
--environment sandbox ./manifests/
Error: Evaluation Error: Error while evaluating a Function Call, Lookup of
key 'classes' failed: The Lookup Configuration at
'/etc/puppetlabs/code/hiera.yaml' has wrong type, entry 'hierarchy' index 0
expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 1 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 2 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, unrecognized key 'backends'
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, unrecognized key 'yaml' in The Lookup Configuration at
'/etc/puppetlabs/code/hiera.yaml' has wrong type, entry 'hierarchy' index 0
expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 1 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 2 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, unrecognized key 'backends' The Lookup Configuration at
'/etc/puppetlabs/code/hiera.yaml' has wrong type, unrecognized key 'yaml'
at /etc/puppetlabs/code/environments/sandbox/manifests/hieraclasses.pp:6:1
on node fenix.harmonywave.co
Clearly the types have changed. However if hierarchy now expects a Struct,
what is the key that should be used? Also backends seems to be depreciated
now.
If anybody has information and/or documentation on the new format could you
please point me to that.
Thanks,
Joshua
On Monday, February 6, 2017 at 2:37:37 PM UTC-7, Thomas Müller wrote:
>
> This is a new deprecation introduced with puppet 4.9.0 (puppet-agent
> 1.9.0).
>
> A related bug: https://tickets.puppetlabs.com/browse/PUP-7171
>
> I too can't find docs to the new format .
>
> - Thomas
>
>
--
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/0d454f4b-8b38-40be-98fa-e56d428491bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
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}"
- common
yaml: datadir: /etc/puppetlabs/code/environments/%{::environment}/hieradata
Here are the errors I get:
root@fenix:/etc/puppetlabs/code/environments/sandbox# puppet apply
--environment sandbox ./manifests/
Error: Evaluation Error: Error while evaluating a Function Call, Lookup of
key 'classes' failed: The Lookup Configuration at
'/etc/puppetlabs/code/hiera.yaml' has wrong type, entry 'hierarchy' index 0
expects
a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 1 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 2 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, unrecognized key 'backends'
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, unrecognized key 'yaml' in The Lookup Configuration at
'/etc/puppetlabs/code/hiera.yaml' has wrong type, entry 'hierarchy' index 0
expects
a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 1 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, entry 'hierarchy' index 2 expects a Struct value, got String
The Lookup Configuration at '/etc/puppetlabs/code/hiera.yaml' has wrong
type, unrecognized key 'backends' The Lookup Configuration at
'/etc/puppetlabs/code/hiera.yaml' has wrong type, unrecognized key 'yaml'
at /etc/puppetlabs/code/environments/sandbox/manifests/hieraclasses.pp:6:1 on
node fenix.harmonywave.co
Clearly the types have changed. However, if hierarchy now expects a Struct,
what is the key that should be used? If anybody has information and/or
documentation on the new format could you please point me to that.
Thanks,
Joshua
On Monday, February 6, 2017 at 2:37:37 PM UTC-7, Thomas Müller wrote:
>
> This is a new deprecation introduced with puppet 4.9.0 (puppet-agent
> 1.9.0).
>
> A related bug: https://tickets.puppetlabs.com/browse/PUP-7171
>
> I too can't find docs to the new format .
>
> - Thomas
>
>
--
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/2905b5f3-5280-4bef-a6c0-f8b95460e295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
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/6399aa7e-a509-4fb5-b9cf-6a95e80f5b4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
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 environment_data_provider = hiera 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/d32d9920-488d-4679-9691-cff6c11ebd3a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
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 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/54a884c0-977e-4548-8d3a-89240173f8d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
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-5f8d3289%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
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. https://docs.puppet.com/puppet/4.9/lookup_quick.html#there-are-two-hierayaml-formats-now This is an interim update while the docs team work on the full update, which will be out in the next week or two. --eric0 On Tuesday, February 14, 2017 at 9:22:53 AM UTC-8, Bob wrote: > > 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 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/5f3712f1-90a2-4f19-8447-9bffdbc77239%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
