# Order of Execution: tasks vs notify

**URL:** <https://forum.ansible.com/t/order-of-execution-tasks-vs-notify/11816>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [August 21, 2012, 8:32pm UTC](https://forum.ansible.com/t/order-of-execution-tasks-vs-notify/11816 "2012-08-21T20:32:54Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [August 21, 2012, 8:32pm UTC](https://forum.ansible.com/t/order-of-execution-tasks-vs-notify/11816/1 "2012-08-21T20:32:54Z")

</div>

What you are doing is a very non-idempotent setup module, so there's  
really no point to your usage of handlers.

I would find it much better to template out the /etc/apache2/.htdigestUser file.

I'd use the template module and remove the shell logic because without  
a "creates=" the shell module is always going to return changed and if  
you run it again, you're going to keep adding lines to that file,  
which  
seems quite undesirable.

---

<div class="post-metadata">

**Author:** ![\_harsha](https://avatars.discourse-cdn.com/v4/letter/_/ecae2f/32.png) [@\_harsha](https://forum.ansible.com/u/_harsha)\
**Post date:** [August 22, 2012, 10:15pm UTC](https://forum.ansible.com/t/order-of-execution-tasks-vs-notify/11816/2 "2012-08-22T22:15:48Z")

</div>

Thank you! This is what I wanted to hear “What you are doing is a very non-idempotent setup module, so there’s  
really no point to your usage of handlers.”

"… you’re going to keep adding lines to that file… " - That was my intended use for this playbook for a shared server. But then again based on what you just said I’ll take a look and see if templating does the job and keep the group posted.