>> No not necessarily, you need to enable resource purging with resources
>> like nagios_host:
>>
>> resources { "nagios_host":
>> purge => true,
>> }
>
>
> Oh, I just did not now that. My manifest now looks like this:
>
> resources { ["nagios_host", "nagios_service"]:
> purge => true,
> }
>
> #Collect the nagios_host resources
> Nagios_host <<||>> {
> target => "/etc/icinga/puppet.d/hosts.cfg",
> require => File["/etc/icinga/puppet.d/hosts.cfg"],
> notify => Service[icinga],
> }
>
> But the entries don't get purged. Looks like I'm still missing something :/
>
>
>
> I think you are running into this:
>
> "You can purge Nagios resources using the resources type, but only in the
> default file locations. This is an architectural limitation."
>
> https://docs.puppetlabs.com/references/latest/type.html#nagioscommand
>
> i.e. if you set the target parameter, you lose the ability to purge.
Well spotted Jonathan ... :-).
So Kai, you can provide fake this with soft-links to the icigna dir
from the expected nagios configuration directory. Or soft-link the
files themselves, up to you.
ken.
--
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/CAE4bNTme_hcT%3DWitVy3%3DLMqmP2rZu%3DB32MNidHovp8D%2B3s8kVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
