If this is the wrong list, please let me know. I'm emailing puppet-dev since
this is firmly in the realm of Puppet code rather than typical manifest
implementation.
I'm not sure if this is a bug or if I'm doing it wrong, so any help is
appreciated. This issue exposed itself while I was working on my Bacula
type/provider and I have confirmed that it is also a problem with Naginator.
Using Naginator as the example, if I have a manifest like this:
nagios_host { "test1":
alias => "alias1",
address => "address1",
}
nagios_contactgroup { "test2":
target => "/etc/nagios/nagios_host.cfg",
alias => "alias2",
}
Only one of the changes will go through at a time. If I add another
nagios_host to the manifest, either both nagios_host configurations or the
nagios_contactgroup configuration will go through.
What I suspect is probably very different than the reality, but here it is
anyway: provider instances for a given type share the @records value so
modifications to one are reflected in all of them.Different types don't
share @records values, so flushing leaves the last man standing.
Obviously, I still haven't figured out the exact details. Can anyone shed
any light on this?
-Shawn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
