complex_args is actually a hashtable where the key is the module option and the value is the raw value for that option. You might be confusing the ArrayList with the generic list we use to store variable definitions, that include complex_args, that are passed to the module_wrapper process.
Anything that uses our exec_wrapper process will use $complex_args even in non-pipelined scenarios as pipelining just changes how the payload is delivered. The only reason why we still read from $args is purely for legacy reasons and for people manually running the modules outside of our wrapper process, i.e. not Ansible. Thanks Jordan -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/76856c43-109a-426a-a8c7-5700056a7945%40googlegroups.com.
