Issue #4146 has been updated by Jeff Weiss. Assignee set to Jeff Weiss Keywords set to nagios module
I think I understand what the goal here is, but it's always good to clarify. We're taking the various nagios types <code>[nagios_command, nagios_contact, nagios_contactgroup, ... , nagios_timeperiod]</code> and moving them from--a Ruby definition in--Puppet proper to a module--defined using the Puppet language--that will be available (via the forge?), yes? I'm worried about a breaking change if we have all the nagios types in a single module. Because of what's in [Defined Types in Modules documentation](http://docs.puppetlabs.com/learning/definedtypes.html#defined-types-in-modules) about each module type being namespaced, won't we end up with [nagios::command, nagios::contact, nagios::contactgroup, ... , nagios::timeperiod] as the new types, breaking manifests that had previously used the _ version? I think we can make a separate module for each of the commands that will maintain manifest continuity, but that's 14 separate modules, which doesn't seem ideal either. ---------------------------------------- Refactor #4146: Move Nagios types and supporting from core to a module https://projects.puppetlabs.com/issues/4146#change-57995 Author: James Turnbull Status: Accepted Priority: Normal Assignee: Jeff Weiss Category: nagios Target version: 2.7.x Affected Puppet version: 0.25.5 Keywords: nagios module Branch: As description says. -- 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.
