Issue #3498 has been updated by Luke Kanies. Status changed from Needs design decision to Rejected Assigned to changed from Luke Kanies to James Turnbull
I think Peter is right - I think this is the expected behaviour. No it's not the prettiest, but I don't see much of a way to fix it, given the constraints. Do you? Obviously, reopen if you disagree with the basic conclusion. ---------------------------------------- Bug #3498: Nagios types don't generate "name" appropriately http://projects.puppetlabs.com/issues/3498 Author: James Turnbull Status: Rejected Priority: High Assigned to: James Turnbull Category: nagios Target version: 0.25.6 Affected version: 0.25.4 Keywords: Branch: The following resource: <pre> @@nagios_service { "check_ping_${hostname}": use => 'generic-service', check_command => 'check_ping!100.0,20%!500.0,60%', host_name => "$fqdn", target => '/etc/nagios3/conf.d/nagios_service.cfg', } </pre> generates the following output: <pre> define service { check_command check_ping!100.0,20%!500.0,60% host_name baal.puppetlabs.com ## --PUPPET_NAME-- (called '_naginator_name' in the manifest) check_ping_baal use generic-service } </pre> The line: <pre> ## --PUPPET_NAME-- (called '_naginator_name' in the manifest) check_ping_baal </pre> should be: <pre> service_description check_ping_baal </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
