Jira (PUP-5924) The default hiera.yaml file does not include the '::' prefix for the environment variable

[Rob Nelson (JIRA)]

Title: Message Title

Rob Nelson commented on PUP-5924   Re: The default hiera.yaml file does not include the '::' prefix for the environment variable Well, I cannot get this to replicate now. I stood up a brand new EL7 image that had the PC1 repo and installed and started puppetserver, nothing more. It has the default hiera.yaml: [root@master ~]# yum install -y puppetserver [root@master ~]# systemctl start puppetserver [root@master ~]# cat /etc/puppetlabs/code/hiera.yaml --- :backends: - yaml :hierarchy: - "nodes/%{::trusted.certname}" - common   :yaml: # datadir is empty here, so hiera uses its defaults: # - /etc/puppetlabs/code/environments/%{environment}/hieradata on *nix # - %CommonAppData%\PuppetLabs\code\environments\%{environment}\hieradata on Windows # When specifying a datadir, make sure the directory exists. :datadir: I then set up a simple common.yaml and site.pp to notify on what is found in common. Running puppet agent gives me what I expect: [root@master ~]# cat /etc/puppetlabs/code/environments/production/hieradata/common.yaml --- key: value [root@master ~]# cat /etc/puppetlabs/code/environments/production/manifests/site.pp node default { $key = hiera('key') notify{"key is $key":} } [root@master ~]# puppet agent -t --server master.nelson.va Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for master.nelson.va Info: Applying configuration version '1456675830' Notice: key is value Notice: /Stage[main]/Main/Node[default]/Notify[key is value]/message: defined 'message' as 'key is value' Notice: Applied catalog in 0.02 seconds Now I change the :datadir: to explicitly state the default, or to have the :: prepend: :datadir: /etc/puppetlabs/code/environments/%{environment}/hieradata :datadir: /etc/puppetlabs/code/environments/%{::environment}/hieradata But no matter what I do, I get the same result from the agent. I was running into this issue during a bootstrap of a new master and the hiera configuration was NOT the only variable. It appears one of those other variables must be the root cause. I'll close this ticket out now and I apologize for taking up your time on this! Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.