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/bl
For starter you may look at
mine: https://github.com/mz0/ansible-digitalocean
So far it deals with one host, that part needs a thought.
On Tuesday, November 20, 2018 at 9:00:51 PM UTC+3, Sloan Miller wrote:
>
> I am currently setting up to add a couple of thousand servers into ansible
> config m
On Sat, Nov 24, 2018 at 12:25 PM Kai Stian Olstad <
ansible-project+l...@olstad.com> wrote:
> On Thursday, 22 November 2018 12:22:42 CET Mark Zhitomirski wrote:
> > Traditional approach is to leave it to a human operator and warn him of
> a
> > new host key.
> > This
On Sat, Nov 24, 2018 at 12:25 PM Kai Stian Olstad <
ansible-project+l...@olstad.com> wrote:
> On Thursday, 22 November 2018 12:22:42 CET Mark Zhitomirski wrote:
> > Traditional approach is to leave it to a human operator and warn him of
> a
> > new host key.
> > This
can you kindly present your case? It's not easy to see what you are trying
and where it fails.
Regards,
Mark
On Tue, Nov 27, 2018 at 7:58 PM wrote:
> As far as I have seen, it is not trivial - looks like although plugin for
> network_cli is selected, the paramiko_ssh plugin is used to handle ac
Hi!
My very limited knowledge of Ansible says it needs SFTP or at least SCP
subsystems on the controlled side.
Your company firewall allows only running ssh interactively - most probably
it's not sufficient for Ansible.
M.
On Wed, Nov 28, 2018 at 6:49 AM Easy King wrote:
> My firm's policy has
h as a regular connector plugin).
> I hope that this helps.
> Thanks,
> Vladan
>
> On Wednesday, 28 November 2018 09:45:35 UTC, Mark Zhitomirski wrote:
>>
>> can you kindly present your case? It's not easy to see what you are
>> trying and where it fails.
>
