On 28/02/17 20:22, Joshua Schaeffer wrote:
The docs on lookup()
<https://docs.puppet.com/puppet/4.9/lookup_quick.html>. state that in
order to upgrade to to hiera v5 you should follow the below list:

      * Change any |hiera|/|hiera_array|/|hiera_hash| calls in your
        manifests to use |lookup| instead.

      * Set |environment_data_provider = hiera| in |puppet.conf|.
        (Individual environments can override this
        in |environment.conf| if needed.)

      * Create a |hiera.yaml| (version 5) file in each environment,
        recreating your existing hierarchy. See below for the file
        format.
        
<https://docs.puppet.com/puppet/4.9/lookup_quick.html#there-are-two-hierayaml-formats-now>

      * Edit your classic |hiera.yaml| config to use a datadir outside
        your environments (like |/etc/puppetlabs/code/hieradata|), so
        that classic Hiera won’t interfere with the new environment data
        provider.


Specifically, it states to set the environment_data_provider. However
when I do this on puppet 4.9.2 I get a warning when I do a lookup
subcommand. This is after setting environment_data_provider in my
environment.conf file

|
#puppet lookup classes --explain
Info:Loadingfacts
Warning:Definingenvironment_data_provider='hiera'inenvironment.conf
isdeprecated.A 'hiera.yaml'file should be used instead
   (in/etc/puppetlabs/code/environments/production/environment.conf)
Searchingfor"lookup_options"
|

When I set it in my puppet.conf file, I get a similar warning:

|
# puppet lookup classes --environment sandbox --explain
Warning:Setting'environment_data_provider'isdeprecated.
   (at
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:584:in`block
in <module:Puppet>')
Info: Loading facts
Info: Loading facts
Warning: Defining environment_data_provider='hiera' in environment.conf
is deprecated
   (in /etc/puppetlabs/code/environments/sandbox/environment.conf)
|

I found this was necessary when working with PE 2016.02 which runs
puppet 4.5.2 and uses hiera v4.


Yes, so the (experimental) v4 support is still present but it is deprecated in puppet 4.9.0 - and that is why it started to present warnings.

- henrik

--
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 [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/c973007e-f2d5-4d26-8888-b955e03d324b%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/c973007e-f2d5-4d26-8888-b955e03d324b%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.


--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/o96d4g%24jpo%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to