Gilles Cornu f96636587a provisioners/ansible: don't read/write known_hosts ... Like Vagrant's default SSH behaviors (e.g ssh or ssh-config commands), the Ansible provisioner should by default not modify or read the user known host file (e.g. ~/.ssh/known_hosts). Given that `UserKnownHostsFile=/dev/null` SSH option is usually combined with `StrictHostKeyChecking=no`, it seems quite reasonable to bind the activation/disactivation of both options to `host_key_checking` provisioner attribute. For the records, a discussion held in Ansible-Development mailing list clearly confirmed that there is no short-term plan to adapt Ansible to offer an extra option or change the behavior of ANSIBLE_HOST_KEY_CHECKING. For this reason, the current implementation seems reasonable and should be stable on the long run. Close #3900 Related References: - https://groups.google.com/forum/#!msg/ansible-devel/iuoZs1oImNs/6xrj5oa1CmoJ - https://github.com/ansible/ansible/issues/9442		2014-11-30 09:55:48 +01:00
..
docs	provisioners/ansible: don't read/write known_hosts	2014-11-30 09:55:48 +01:00
www	Explain that older Vagrant plugin licenses may not work with new VMware	2014-11-04 10:46:54 -05:00