The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Feature #7594

It should be possible to trigger specific actions with notify/subscribe relationships.

Added by Nigel Kersten almost 5 years ago. Updated over 4 years ago.

Status:AcceptedStart date:05/19/2011
Priority:HighDue date:
Assignee:-% Done:


Target version:3.x
Affected Puppet version: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


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):

file { "foo.conf":
  notify => Service["foo"].stop,

service { "foo":
  notify_action => "reload",

Related issues

Related to Puppet - Feature #1014: Services should support 'reload' in addition to 'restart' Accepted
Duplicated by Puppet - Feature #7332: resource pre / post condition on e.g. service status Duplicate 05/03/2011


#1 Updated by Robert Voje almost 5 years ago

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.

Also available in: Atom PDF