On Wednesday, August 14, 2013 12:57:17 PM UTC+10, Henrik Lindberg wrote:
I was hoping that it would derive the hiera.yaml path dynamically from
the clients' environment when it checks in, but this seems not to be the
case.
That is correct, it does not do that.
- henrik
I am
On Wednesday, June 18, 2014 10:47:20 AM UTC+10, Alex Harvey wrote:
I am also encountering this issue (puppet 3.3.1) - is it still a known
issue?
Ignore - I found the open Jira ticket here
https://tickets.puppetlabs.com/browse/HI-46
--
You received this message because you are subscribed
Hi Pablo,
Thanks for the response.
I've tried setting the environment in the master section, the agent
section, the main section.
Regardless of whether I set the environment anywhere in the masters
puppet.conf, it always looks for the hiera.yaml file in the production
directory.
I was hoping
On 2013-13-08 24:25, jamese wrote:
Hi Pablo,
Thanks for the response.
I've tried setting the environment in the master section, the agent
section, the main section.
Regardless of whether I set the environment anywhere in the masters
puppet.conf, it always looks for the hiera.yaml file in the
Hi James,
One thing to take into account here is that hiera_config is under the
[master] section, so it might not take into account settings in
[agent], such as the environment.
Try running puppet master --configprint environment to see if it's set
to the default (which is production).
Hope this
Hi all,
I'm playing with a new setup of puppet 3.2.3 and hiera 1.2.0 on an EL6
server.
The puppet config is stored in a git repo (as per
https://puppetlabs.com/blog/git-workflow-and-puppet-environments/*)*
I want to use a separate hiera.yaml file per environment, so in the
puppet.conf, I
