On Mon, Aug 05, 2013 at 04:22:41PM -0400, Gabriel Filion wrote:
>
> you need to export the resource with ensure => absent and run puppet on
> the host, then on the nagios server so that everything runs fine.
Dozens of VMs are routinely destroyed on a weekly basis and in an
automated fashion based on load. The nagios_*.cfg files are
automatically changed, why is the notify not triggering?
> however in your example, you seem not to be redefining the "target" when
> collecting, so you might consider using purge => true. to achieve what
> you want with the workflow you mentioned above (e.g. without the need to
> export with ensure => absent)
I am purging unless you are referring to a different resource stanza.
>From my OP:
resources { [ "nagios_host", "nagios_service" ]:
purge => true,
}
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
