Issue #7594 has been updated by Robert Voje.
Don't forget that if the service is to be restarted, all reload actions must be cancelled, to avoid that the service is both reloaded and restarted. Maybe a kind of priority level between reload and restart. ---------------------------------------- Feature #7594: It should be possible to trigger specific actions with notify/subscribe relationships. https://projects.puppetlabs.com/issues/7594 Author: Nigel Kersten Status: Accepted Priority: High Assignee: Category: Target version: Telly Affected Puppet version: Keywords: Branch: Currently if a Service or Exec receives a notify event, it refreshes. We need more fine-grained control than this. There are common use cases where you want to specify that the service should be started or stopped instead. Ideally we want to be able to both specify this at the sender specifically, and at the receiver as a default value, e.g. (not actual proposed syntax at all): <pre> file { "foo.conf": notify => Service["foo"].stop, } service { "foo": notify_action => "reload", } </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.
