Issue #19343 has been reported by James Shubin.
----------------------------------------
Bug #19343: FWIW, puppetmaster doesn't notice changes to /etc/puppet/hiera.yaml
https://projects.puppetlabs.com/issues/19343
Author: James Shubin
Status: Unreviewed
Priority: Low
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
<pre>
If you change the :hierarchy: in /etc/puppet/hiera.yaml to add or remove a file
foo (eg: foo.yaml) puppetmaster and it's clients won't notice this until you
restart it. Ideally it would notice this with a mechanism such as inotify or
similar.
This can be an issue if you've added a classname::param: value entry in a new
file, and you now expect the automatic hiera lookups to see these changes.
Similarly, you might have removed or reordered the hierarchy, and you won't see
these changes until the server reloads.
As a workaround for those who manage their hiera.yaml and puppetmaster service
with puppet you could add:
file { '/etc/puppet/hiera.yaml':
notify => Service['puppetmaster'],
}
Hopefully this report helps!
Cheers!
</pre>
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.