2.3 removed this unfortunately with the way the execution wrapper now works. I believe Matt was looking at reverting the behavior to what it was before when ANSIBLE_KEEP_REMOTE_FILE is set to true but I'm not sure where he is at with that. Unfortunately this means in the meantime I'm stuck with putting in lots of Fail-Jsons to try and debug what is happening or run the module with a 2.2 install.
On Tuesday, April 25, 2017 at 9:59:24 PM UTC+10, Trond Hindenes wrote: > > Previously we could configure ansible to leave files in the user's temp > dir in order to troubleshoot/debug Powershell modules. In 2.3.0 all of this > got rewritten, so it seems that option is gone. > > Being able to troubleshoot the "generated" files is completely crucial (at > least for me) when developing and troubleshooting things. What are my > options for debug/troubleshooting Powershell with Ansible going forward? > -- 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. For more options, visit https://groups.google.com/d/optout.
