# Preventing a deploy of tomcat from running again.

**URL:** <https://forum.ansible.com/t/preventing-a-deploy-of-tomcat-from-running-again/17972>\
**Category:** Ansible Project\
**Created:** [April 14, 2015, 8:56am UTC](https://forum.ansible.com/t/preventing-a-deploy-of-tomcat-from-running-again/17972 "2015-04-14T08:56:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Brooks](https://avatars.discourse-cdn.com/v4/letter/c/9de053/32.png) [@Chris\_Brooks](https://forum.ansible.com/u/Chris_Brooks)\
**Post date:** [April 14, 2015, 8:56am UTC](https://forum.ansible.com/t/preventing-a-deploy-of-tomcat-from-running-again/17972/1 "2015-04-14T08:56:36Z")

</div>

Hiya,

I’ve had a google for this but I can’t find anything which answer my question…

I have a playbook which deploys tomcat via a zip file, this is the standard tomcat file from their website.

it then takes a template of server.xml and places it in the /opt/tomcat/conf directory.

This action changes the contents so the next time my playbook runs it re-runs the play which I don’t want, is there an easy way around this?

This is the relevant section:-

---

<div class="post-metadata">

**Author:** ![Edgars](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@Edgars](https://forum.ansible.com/u/Edgars)\
**Post date:** [April 14, 2015, 12:23pm UTC](https://forum.ansible.com/t/preventing-a-deploy-of-tomcat-from-running-again/17972/2 "2015-04-14T12:23:06Z")

</div>

unarchive module supports creates parameter:

> > creates | : | |   
> >   
> > | a filename, when it already exists, this step will **not** be run. (added in Ansible 1.6) |
> > 
> > - | - | - | - | - |

Edgars

otrdiena, 2015. gada 14. aprīlis 13:16:03 UTC+2, Chris Brooks rakstīja: