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.
I've just thought about that: maybe I could get what I want by setting a
default value to some parameters to the define? for example, if I'd like
to define some groups depending on an arbitrary "level" of service :
class level1_apache_server {
Nagios::Service {
base_groups => 'level1-apache-server',
}
include apache_logic
}
I think I remember seeing discussion about this kind of feature getting
killed sometime because of scoping issues.. is that right?
--
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.
