# Proposal: module to dump available data structures in a playbook

**URL:** <https://forum.ansible.com/t/proposal-module-to-dump-available-data-structures-in-a-playbook/12534>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [March 19, 2013, 10:00pm UTC](https://forum.ansible.com/t/proposal-module-to-dump-available-data-structures-in-a-playbook/12534 "2013-03-19T22:00:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [March 19, 2013, 10:00pm UTC](https://forum.ansible.com/t/proposal-module-to-dump-available-data-structures-in-a-playbook/12534/1 "2013-03-19T22:00:12Z")

</div>

Per discussion on the list, I think I like the idea of just using the  
template module to do this, and then showing how to do this on  
coderwall and in the docs.

Otherwise we end up duplicating too much logic to have a  
single-purpose template.

It may also be possible to do something interesting with  
ansible-commander and callbacks down the road, to see the effective  
variables before and at the end of plays (TBD).