-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fragments from multiple hiera hierarchies #41
Comments
at line 59 of manifests/init.pp change it to look like https://github.com/ghoneycutt/puppet-module-ssh/blob/master/manifests/init.pp#L549-558 If you specify the option, we want the ability to use hiera_hash() which will pull all of the found fragments instead of stopping at the first one. |
Brilliant, thank you! Are you going to make this patch on your own, or would you like me to issue a pull request? I added at line 10: And changed the code block at line 59 to read: if $rsyslog_fragments != undef { And enable it via rsyslog::hiera_merge: true in my hiera yaml definition. |
Woops, left an extra notice debug in my paste by mistake. |
Could you please submit a pull request and close this issue? I'm more than happy to help you through the process. |
I have a couple hierarchies in hiera as follows:
:hierarchy:
When specifying rsyslog fragments in multiple hierarchies, the first match is treated exclusively. I'm sure this is expected behavior due to the hiera syntax, I'm curious if you know of a good way around it without duplicating code?
ie. in global.yaml:
rsyslog::rsyslog_fragments:
5-rate-limits:
content: "$SystemLogRateLimitInterval 0\n$SystemLogRateLimitBurst 0\n"
then in hostgroup/somegroup.yaml:
rsyslog::rsyslog_fragments:
somegroup:
content: ". @@somegroup.logserver"
"somegroup" is retained in /etc/rsyslog.d/ and 5-rate-limits is completely ignored. It would be great to have them combine, if at all possible?
The text was updated successfully, but these errors were encountered: