I usually just run something like this:

ansible -m debug -a "var=hostvars['interesting_host']" localhost -i 
test_inventory

Hope this helps,

Jon

On Friday, May 27, 2016 at 4:21:52 PM UTC+1, Andy L wrote:
>
> Prior to 2.0, I used a task that dumped Ansible variables to an output 
> file using a template.
>
> This technique was super valuable for debugging.
>
> The template looked like this:
>
> HOST Variables ("hostvars"):
> --------------------------------
> {{ hostvars | to_nice_json }} 
>
> Module Variables ("vars"):
> --------------------------------
> {{ vars | to_nice_json }}
>
> In 2.0 and 2.1, these no longer work.
>
> Questions:
> 1) Can anyone post a workaround for these bugs?
> 2) By now Ansible should be mature.  How did this regressions not get 
> caught?  Is Ansible tested?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/80696c54-0399-4a4d-879e-8c384992977b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to