I used the shell provisioner to launch a script that setup Ansible and then used Ansible in pull mode.
IIRC I was able to issue management commands via vagrant ssh (ie from Windows command prompt). On Monday, December 9, 2013 8:51:07 AM UTC-6, Taylor Brown wrote: > > > > Using Vagrant to spin up dev environments promises to end many of our > cross-platform server-side development issues once and for all. When > deciding how to provision my vagrant boxes, I considered Chef, Puppet, and > Ansible. I settled on Ansible for reasons that are obvious to this group's > readers. :) After getting my Vagrant-based Postgres box provisioned with > Ansible, I realized that I ironically painted us into another > cross-platform corner once again! My Windows devs won't be able to use the > Ansible provisioner at all. At this point, I can either package my Vagrant > .boxes and ship them to the Windows devs, or I can try to get them to install > Cygwin and other > dependencies<http://dhorbach.blogspot.com.ar/2013/08/working-with-ansible-in-eclipse-and.html>and > hope for the best. > > So, I guess this post has two purposes: > 1) to throw another vote towards using Ansible from Windows hosts > (specifically for Vagrant) > 2) To ask what other folks have done with my predicament? I'm guessing > folks use Chef or Puppet for cross platform provisioning of Vagrant boxes? > > Taylor > -- 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 ansible-project+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
