# play level notifications

**URL:** <https://forum.ansible.com/t/play-level-notifications/11556>\
**Category:** Ansible Project\
**Created:** [May 18, 2012, 1:33am UTC](https://forum.ansible.com/t/play-level-notifications/11556 "2012-05-18T01:33:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthew\_Williams](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@Matthew\_Williams](https://forum.ansible.com/u/Matthew_Williams)\
**Post date:** [May 18, 2012, 1:33am UTC](https://forum.ansible.com/t/play-level-notifications/11556/1 "2012-05-18T01:33:07Z")

</div>

For a future release, I would like to propose a feature that would allow a ‘global’ notification parameter. The specified handler(s) would fire if any of the tasks in the play registered a change. This would be handy when uploading a series of config files, any of which should restart the service.

Example syntax:  
[https://gist.github.com/17b1d3c4d0d53feb27ec](https://gist.github.com/17b1d3c4d0d53feb27ec)

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [May 18, 2012, 2:23am UTC](https://forum.ansible.com/t/play-level-notifications/11556/2 "2012-05-18T02:23:01Z")

</div>

FWIW, upload vhost could be done with a “with\_items” in which case I think change handlers “just work”.

I’m not sure how often a global handler would make sense, and in some cases if you, say, add a user, you might not need to restart the service.

Following what the other CM tools do in this case, I don’t think a global notifier makes sense. I think I’d rather it be explicit.