"It also means that unless I hack that file I'm not getting my module to behave similarly. "
Basically we'd have to find some way of putting the metadata in the module versus having it in Runner. This is really a topic for ansible-devel, BTW On Mon, Jan 6, 2014 at 7:52 PM, Dmitry Makovey <[email protected]> wrote: > I think I've got it: > > http://pastebin.com/NCgAhVjF > > now works with: > > - name: Testing Foo dicts > foo: > name: > one: 1 > two: 2 > three: 3 > state: present > > - name: Testing Foo lists > foo: > name: [ 1, 2, 3] > state: present > > - name: Testing Foo lists > foo: > name: > - 1 > - 2 > - 3 > state: present > > last two result in a simple list iteration, while the first one passes > dictionary this should help with my module building... unless somebody is > going to point out a better way/inapropriateness of my approach :) > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
