Is there documentation on Windows module development workflow?
My edit-debug cycle is extremely long. I think there should be a shorter path?
I edit the windows module (win_chocolatey in this case) on my testing linux ansible control host, run my test playbook with ANSIBLE_DEBUG=1, ANSIBLE_KEEP_REMOTE_FILES and -vvvvv, and suffer the lack of interactive debugging.
The developing modules documentation seems to be high level details and related to developing modules in python. I cannot find similar information for developing modules in powershell.
Just looking for advise to shorten the debug cycle.
However the list of things to do is extensive and at the moment some of us are improving the integration tests and general quality of the existing Windows modules, and working on the issue/PR backlog.
If you are interested in helping out (and you are well-placed to improve these docs) you can join our bi-weekly Windows Working Group meetings, ask questions and write the missing pieces of the documentation. That would be very welcome.