# unarchive dry-run is never changed

**URL:** <https://forum.ansible.com/t/unarchive-dry-run-is-never-changed/26163>\
**Category:** Ansible Project\
**Created:** [November 29, 2017, 7:52am UTC](https://forum.ansible.com/t/unarchive-dry-run-is-never-changed/26163 "2017-11-29T07:52:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christophe\_Pache](https://avatars.discourse-cdn.com/v4/letter/c/f1d935/32.png) [@Christophe\_Pache](https://forum.ansible.com/u/Christophe_Pache)\
**Post date:** [November 29, 2017, 7:52am UTC](https://forum.ansible.com/t/unarchive-dry-run-is-never-changed/26163/1 "2017-11-29T07:52:23Z")

</div>

Hello everyone!

I’m quite new to ansible and I’m trying to test the --check command and to understand how much I can test the deployed system with. I’m deploying an archive and extracting it to a folder and would like to use the dry-mode of ansible to check if the folder contains the right things. I expected the dry-run to do this check but, changing files manually, I keep getting changed=0. Doc states:

> Uses gtar’s –diff arg to calculate if changed or not. If this arg is not supported, it will always unpack the archive.

Could someone confirm if it’s working with dry-run? Should I implement my own task to run a tar diff to check it?

Thanks a lot!  
Christophe