Re: [ansible-devel] Re: win_command with become still doesn't seem to work

2019-02-15 Thread Christopher Perrin
Maybe you could try the win_chocolatey. It has a VS2017 package - name: install VS2017 win_chocolatey: name: visualstudio2017enterprise package_params: "--add Microsoft.VisualStudio.Workload.NativeDesktop" state: present I have not tested this. But maybe this is more stable than the

Re: [ansible-devel] Re: win_command with become still doesn't seem to work

2019-02-14 Thread Mike V
Thank you Jordan! I just tried the suggestion and it works great! I agree, the installer is terrible to begin with. I initially wanted to do a chocolatey package but it was overwhelmingly even more complex too learn for this type of installer. I really appreciate your help and test On Thu, Feb

[ansible-devel] Re: win_command with become still doesn't seem to work

2019-02-14 Thread Jordan Borean
I found some time to play around with this a bit more. It turns out the initial installer spawns multiple processes and doesn't actually wait until it is finished. This causes the parent WinRM process to close it's shell which has the side affect of killing any children it spawns. It's weird be

[ansible-devel] Re: win_command with become still doesn't seem to work

2019-02-13 Thread Jordan Borean
Just a few things to note, you don't need to set the task directory become, become_method, become_user if you have set the vars as well. Variable > than task directives when it comes to precedence. If the initial exe is then starting up another executable and exits immediately it makes sense th