It would really nice if it would be possible to control this on the group_var or host_var level, too. So instance for dev environments with vagrant one could just disable host key checking but for production environments it would still work...
Am Mittwoch, 3. Juli 2013 23:02:10 UTC+2 schrieb Michael DeHaan: > > Various folks did not like the fact that we disabled strict SSH host key > checking to more easily enable reprovisioning related use cases. Their > concerns are valid, and we should have a way to control this behavior. > > In the latest 1.3, Strict checking is now on by default for both paramiko > and SSH connection types. > > Should you wish to disable this, you can, by either > > export ANSIBLE_HOST_KEY_CHECKING=False > > or in the config file > > [defaults] > host_key_checking=False > > I plan to cherry-pick this commit to 1.2 and cut a 1.2.1 containing only > this change providing this works for everyone. > > > > -- > Michael DeHaan <[email protected] <javascript:>> > CTO, AnsibleWorks, Inc. > http://www.ansibleworks.com/ > > -- 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/af79846a-54ff-4c85-8dfa-f6d8d49ac786%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
