Thanks for those resources, but I already have Ansible set up that I can communicate with a windows server using windows specific modules. The general question was whether those were the only modules that are useable with windows besides "script" and a few others, and whether for most functionality you basically just had to write powershell scripts.
On Wednesday, August 26, 2015 at 6:35:54 PM UTC-4, pixel fairy wrote: > > use on windows is described here > http://docs.ansible.com/ansible/intro_windows.html > > list of windows modules here, > http://docs.ansible.com/ansible/list_of_windows_modules.html > > workaround for a current winrm bug here, > https://github.com/ansible/ansible/issues/10294#issuecomment-93629047 > > that workaround will work for ansible-playbook. to enable the 'ansible' > command itself, put these lines in your ansible.cfg > bin_ansible_callbacks = True > callback_plugins = path/to/fix-ssl.py > > On Wednesday, August 26, 2015 at 2:24:21 PM UTC-7, Joshua Adelman wrote: >> >> I started playing around with Ansible (1.9.2) today for the first time >> (first time using any software in this category before), with the goal of >> running a number of deploy steps on a Windows machine. I went through the >> setup instructions and I believe I have everything configured properly, >> such that I can run playbooks with tasks based on windows-specific modules >> (win_ping, win_stat, etc). >> >> After convincing myself that I could run those basic commands, I wanted >> to try to clone a git repo to the remote Windows machine using the git >> module, but kept on getting error messages like: >> >> Module command not found in configured module paths. Additionally, core >>> modules are missing. >> >> >> I think this warning is specious, since I can run basically the same git >> task locally on my mac through ansible using a modified playbook. It then >> dawned on me that perhaps none of the standard core modules are actually >> supported on windows. Reading through the windows intro in the docs ( >> http://docs.ansible.com/ansible/intro_windows.html) again, I realized >> that the "What modules are available" section is actually a bit vague. >> >> I was hoping someone could clarify, whether it's the case that if a >> module isn't specifically a windows module, then basically it doesn't work >> on windows targets. In that case, am I correct in my understanding that the >> only mode of executing custom tasks on windows targets is to do it via >> powershell scripts (using the "script" module)? >> >> Any insight from more experienced users would be much appreciated. >> >> Thanks, >> Josh >> >> >> -- 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/554ee365-d0d6-4bda-8f24-af18c546876c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
