# Ansible 2.0 VariableManager

**URL:** <https://forum.ansible.com/t/ansible-2-0-variablemanager/19109>\
**Category:** Ansible Developer\
**Created:** [August 25, 2015, 12:58pm UTC](https://forum.ansible.com/t/ansible-2-0-variablemanager/19109 "2015-08-25T12:58:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Victor\_Volle](https://avatars.discourse-cdn.com/v4/letter/v/e8c25b/32.png) [@Victor\_Volle](https://forum.ansible.com/u/Victor_Volle)\
**Post date:** [August 25, 2015, 12:58pm UTC](https://forum.ansible.com/t/ansible-2-0-variablemanager/19109/1 "2015-08-25T12:58:12Z")

</div>

Hi!

In [http://www.slideshare.net/jimi-c/v2-and-beyond?related=1](http://www.slideshare.net/jimi-c/v2-and-beyond?related=1) and [http://www.slideshare.net/jimi-c/whats-new-in-v2-ansiblefest-london-2015](http://www.slideshare.net/jimi-c/whats-new-in-v2-ansiblefest-london-2015) a new improved Variable Management is hinted at but not much more.

Is there anything in the docs, some tutorial _what_ the exact changes are?  
And even more important: how I might be able to adapt/extend that behaviour?

I would like to write my own variable resolution against a “configuration store”

Victor

---

<div class="post-metadata">

**Author:** ![Hagai\_Kariti](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@Hagai\_Kariti](https://forum.ansible.com/u/Hagai_Kariti)\
**Post date:** [August 25, 2015, 1:35pm UTC](https://forum.ansible.com/t/ansible-2-0-variablemanager/19109/2 "2015-08-25T13:35:08Z")

</div>

+1 to that
