f96636587a
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 |
||
|---|---|---|
| .. | ||
| ansible.html.md | ||
| basic_usage.html.md | ||
| cfengine.html.md | ||
| chef_apply.html.md | ||
| chef_client.html.md | ||
| chef_common.html.md | ||
| chef_solo.html.md | ||
| chef_zero.html.md | ||
| docker.html.md | ||
| file.html.md | ||
| index.html.md | ||
| puppet_agent.html.md | ||
| puppet_apply.html.md | ||
| salt.html.md | ||
| shell.html.md | ||