Traditional approach is to leave it to a human operator and warn him of a new host key. This way is a no-go for automation and testing, a workaround is to disable host-key checks with ansible_ssh_extra_args: '-o StrictHostKeyChecking=no' like here: https://github.com/mz0/ansible-digitalocean/blob/186eb84df/launch.yml#L53
It seems to me that a better way would be to auto-add host-key if this is a wholly new host (and maybe check for key uniqueness). My understanding is that this is a job for a certain Ansible plugin, cause host-key handling is not dependent on specific cloud/provisioning module (digital_ocean_droplet in my case) So far I couldn't find any plugin of this sort and kindly ask for pointers. Regards, MZ -- 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/4adc8c21-d5ed-46d9-9f46-57bdfa77c723%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
