# Use Ansible to audit server configs across life-cycle environments?

**URL:** <https://forum.ansible.com/t/use-ansible-to-audit-server-configs-across-life-cycle-environments/26946>\
**Category:** Ansible Project\
**Created:** [March 9, 2018, 5:04pm UTC](https://forum.ansible.com/t/use-ansible-to-audit-server-configs-across-life-cycle-environments/26946 "2018-03-09T17:04:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Len\_S](https://avatars.discourse-cdn.com/v4/letter/l/ecccb3/32.png) [@Len\_S](https://forum.ansible.com/u/Len_S)\
**Post date:** [March 9, 2018, 5:04pm UTC](https://forum.ansible.com/t/use-ansible-to-audit-server-configs-across-life-cycle-environments/26946/1 "2018-03-09T17:04:24Z")

</div>

Does Ansible provide the ability to effectively provide a diff of configuration files of server components across lifecycle environments? I have a requirement to be able to tell if my JVM’s and AppServers have the same configuration across acceptance and production. I know Ansible provides alot more functionality but I’m hoping someone has done a similar kind of thing… Any feedback is appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [March 9, 2018, 5:19pm UTC](https://forum.ansible.com/t/use-ansible-to-audit-server-configs-across-life-cycle-environments/26946/2 "2018-03-09T17:19:24Z")

</div>

Ansible does not do this automatically, but you can use  
fetch/slurp/copy and diff mode to accomplish it.

---

<div class="post-metadata">

**Author:** ![Andrew\_Latham](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@Andrew\_Latham](https://forum.ansible.com/u/Andrew_Latham)\
**Post date:** [March 9, 2018, 5:41pm UTC](https://forum.ansible.com/t/use-ansible-to-audit-server-configs-across-life-cycle-environments/26946/3 "2018-03-09T17:41:31Z")

</div>

You could check for a “file stat get\_md5” and register it for output to a datafile
