# \[dev\] Minor change -- not saving setup data to local disk

**URL:** <https://forum.ansible.com/t/dev-minor-change-not-saving-setup-data-to-local-disk/11416>\
**Category:** Ansible Project\
**Created:** [April 17, 2012, 11:36pm UTC](https://forum.ansible.com/t/dev-minor-change-not-saving-setup-data-to-local-disk/11416 "2012-04-17T23:36:43Z")\
**Posts on this page:** 1\
**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:** [April 17, 2012, 11:36pm UTC](https://forum.ansible.com/t/dev-minor-change-not-saving-setup-data-to-local-disk/11416/1 "2012-04-17T23:36:43Z")

</div>

Just wanted to correct something I had shared earlier.

I thought I needed to save setup variables in order to do local templates. This is actually not true, because this is exactly what  
the SETUP\_CACHE variable holds.

As a result, I will _not_ be saving files in /var/lib/ansible/setup\_data/.

This shouldn’t really affect anyone as the code to this is just a few days old anyway.

If you want those files, you can acquire them using the fetch module.

For those that are confused, to avoid the dependency on python-jinja2 for doing templates, we’re going to be evaluating template data locally  
and sending the resulting files over. This means you will need python-jinja2 only on the Ansible control machine.

–Michael