On 12-04-12 04:18 AM, Luke Bigum wrote: > Could you get by with a wrapper? Say, a 'my_nagios' define that does > it's own thing, then uses the third party 'nagios' definition? > > You could add your own resources in your my_nagios that 'Subscribes' to > resources in the 'nagios' define to insert your own resources into the > dependency chain.
Well, I've thought about that. But the problem with this approach is that all the nagios services defined in other modules to automatically verify services will not be using the 'my_nagios' definition, but still the one from the nagios module. > If you actually need to modify parameters of a resource in a definition > though then the only way I know of would be to have that parameter > controlled by an argument to the defined type. yeah, hence the need to modify the define to add in the additional logic :\ > On 12/04/12 07:10, Gabriel Filion wrote: >> I'm currently using a "nagios" module that's developed by an opensource >> community, and I'd like to hook some logic into a define to implement >> some kind of notion that's really specific to the place I work. >> >> For now, I've been obligated to keep a modified version of the module, >> but that means I always need to rebase re-arrange my code around >> upstream modifications.. and for maintenance, it really adds a bunch of >> work. >> >> Do you guys know if it would be possible to implement a way to "hook" my >> extraneous logic into the define so that I don't need to modify the >> module directly anymore? >> > > -- Gabriel Filion -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
