On Mon, Aug 18, 2014 at 7:29 AM, Michael DeHaan <[email protected]> wrote:
>
> The usage of accept_hostkey=yes is an indication that you are telling it
> manually to trust. Basically it will call (on the module side) the right
> commands to add the fingerprint of the remote server to known_hosts, such
> that you don't have to do manually manage or add it to known hosts.
> Obviously, in doing so, you must trust the remote entity, so not everyone
> may be comfortable with doing this at runtime.
Thank you. That's what I thought.
>
>> "From a Clueless Outsider's perspective, that bug looks like a *very*
>> distant relative."
>
> Nope, it's the same thing. If you specify a new origin repo to the git
> module, it needs to not only blow away the current content to reclone, but
> also consider accepting a new hostkey.
I'm not doing that. Well, not through ansible.
It will not clone ssh://gh/me/{{ item }}.git. So I had it clone
ssh://[email protected]/me/{{ item }}.git instead.
That works fine, except that the user on the freshly-configured host
doesn't have any idea which ssh key to use for that url. So, after
ansible's out of the picture, I've manually run set-url to let me do
things that are part of my normal old-fashioned work flow, like git
pull and push.
--
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/CAEwYyJ5v3xReixyJvB281TObQP%3D21YgZkdS8pXSmJArHt9GJ6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
