It seems that the nagios_service type will not write out the "name" property of nagios service objects. I had thought this was an oversight or a bug, till I saw this thread: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10387.html which seems to imply that this is a deliberate "feature". Is this prohibition on "name" really the desired behaviour? This would make it impossible to use the nagios_service resource to generate a service template that can be reused in other service declarations. If it is the desired behaviour, why does the nagios_service type have "use" and "register" parameters, because they are useless without the ability to attach names to services in the generated nagios config. Hopefully I am just missing something and can be pointed patiently to the way to do what I want. -- Bruce What would Edward Woodward do? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Oct 20, 2010 at 05:16:39PM +0100, Bruce Richardson wrote:> desired behaviour, why does the nagios_service type have "use" and > "register" parameters, because they are useless without the ability to > attach names to services in the generated nagios config.Well, "use" is still functional, because I can always put service templates into puppet templates or just statically copied files, rather than using the nagios_service resource. But setting "register => 0" on a nagios_service type is pointless if you can''t reuse the resulting object, because it has no name. Is it really the case that services, alone out of all the nagios object types, can''t generate object templates from the corresponding puppet type? What I want to do is this kind of thing: nagios_service { ''generic-service'': <whatever> register => ''0'' } nagios_service { ''ping-service'': use => ''generic-service'', service_description => ''Ping'' check_command => ''check_ping!100.0,20%!500.0,60%'', register => ''0'' } and then in some role class... @@nagios_service { "ping_$fqdn": use => ''ping-service'' hostname => $fqdn register => ''1'' } But, unless I''m missing something, I can only do that by creating a file containing nagios service templates via some other route. -- Bruce I must admit that the existence of Disneyland (which I know is real) proves that we are not living in Judea in AD 50. -- Philip K. Dick -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Oct 20, 2010 at 05:16:39PM +0100, Bruce Richardson wrote:> It seems that the nagios_service type will not write out the "name" > property of nagios service objects. I had thought this was an oversight > or a bug, till I saw this thread: > > http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10387.htmlAh, I should have looked further: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10162.html OK, so it''s a bug not a feature. Patching away - need that functionality. -- Bruce Remember you''re a Womble. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.