Dan, this is far from a corner case. Vagrant's default behavior is to
setup the ssh address to: 127.0.0.1:.
Michael, thanks for your hard work on Ansible! It's not that it treats
Vagrant boxes differently, *synchronize* treats localhost and 127.0.0.1
differently, but maybe it shouldn't unl
Here's what I do to gain some other benefits:
- I let Vagrant dynamically generate the hosts file that is later used by
Ansible.
- the Vagrant boxes use a different subnet thus not conflicting with the
corner case described above.
On Wednesday, 13 August 2014 16:59:52 UTC+2, Jeppe Toustrup wrote
Ansible views Vagrant as no different than any other computer.
I believe it should set ansible_ssh_port in inventory.
If you can paste what kind of errors you are seeing and your ansible
version it might be more clear what you're talking about, but I don't
understand "get hit by the special handl
Sorry for bringing up a (somewhat) old topic, but what about the use case
where Ansible is used to configure a Vagrant VM? In that case the VM would
be accessible through 127.0.0.1:, and thus get hit by the special
handling in the synchronization module. This means if you want to write to
a
