Thanks for your answer! I will have another look soon.
It's a bit annoying that modules that were working just fine won't work at all after an update of a minor version. And also to find no information about wether the way we create module changed or not. This being said, I do appreciate that Ansible (especially Windows support) is getting better and better! Love the idea of sharing code between modules. Stuff happens :-) Cheers! On Tuesday, August 22, 2017 at 11:27:29 AM UTC+2, [email protected] wrote: > > Hi there! > > I have a number of custom windows modules for Ansible working fine in 2.2. > I updated today from 2.3.2. and none of these are working anymore... I saw > the same behavior in 2.3.1. > I'm thinking the new "windows pipelining" might be the cause. > > I tried to troubleshoot further. Using the KEEP_REMOTE_FILES=1 env > variable, I was able to check the powershell script and run it manually. > It is actually making both ISE and the powershell console crash without > outputting anything. I narrowed it down to the following line: "$output = > $entrypoint.Run($payload)". > > Did you run into the same issue and managed to fix it? > Any pointer where I could take it from here? Any tip appriciated. > > Cheers, > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b8d16e8c-97fc-4310-9349-3547c6208bc1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
