# debugging modules on ansible =\> 2.3.0 **URL:** \ **Category:** Ansible Developer\ **Created:** [April 25, 2017, 11:59am UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305 "2017-04-25T11:59:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [April 25, 2017, 11:59am UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305/1 "2017-04-25T11:59:24Z")
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? ---
**Author:** ![Sam1](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@Sam1](https://forum.ansible.com/u/Sam1)\ **Post date:** [April 25, 2017, 4:57pm UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305/2 "2017-04-25T16:57:18Z")
Hi Trond, You have actually answered the question I asked yesterday regarding module args so thank you for that! Shame it doesn't work now though 🙂 Coincidentally the reason I wanted to find out was because your win\_dsc5 module isn't respecting check mode in 2.3. If it's something you're seeing too I am happy to raise an issue on Github and help diagnose the problem? ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [April 25, 2017, 9:18pm UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305/3 "2017-04-25T21:18:58Z")
Haha, glad to help Regarding check mode: Yep, please raise an issue in the dsc repo on github and I’ll keep that updated. We’ll be moving the win\_dsc5 module into Ansible core soon, but for now it lives in the repo [https://github.com/trondhindenes/Ansible-win\_dsc](https://github.com/trondhindenes/Ansible-win_dsc) ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [April 25, 2017, 9:29pm UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305/4 "2017-04-25T21:29:47Z")
opened issue: [https://github.com/ansible/ansible/issues/23986](https://github.com/ansible/ansible/issues/23986) ---
**Author:** ![Sam1](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@Sam1](https://forum.ansible.com/u/Sam1)\ **Post date:** [April 25, 2017, 9:33pm UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305/5 "2017-04-25T21:33:14Z")
Good stuff, cheers. Will set aside some time tomorrow ---
**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\ **Post date:** [April 26, 2017, 8:17am UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305/6 "2017-04-26T08:17:27Z")
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. ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [April 26, 2017, 10:18am UTC](https://forum.ansible.com/t/debugging-modules-on-ansible-2-3-0/24305/7 "2017-04-26T10:18:35Z")
yep, lets’ hope he cooks up something 🙂 Its a bit of a pita atm.