Manage ~git/.ssh/config (bitbucket import key)

http://doc.gitlab.com/ce/integration/bitbucket.html#integrate-your-server-with-bitbucket

The bitbucket importer no longer uses the default id_rsa private SSH key for the git user. This means we need to put a section in ~git/.ssh/config to tell the SSH client to use the special bitbucket key when connecting to bitbucket.org.

cc @marin @DouweM

The bitbucket importer in omnibus-gitlab is broken until we fix this.

FYI, I also noticed when I ran the Bitbucket importer for the first time I got this message on my Sidekiq console (running a dev server with bundle exec foreman start):

00:11:34 worker.1 | 2015-08-11T07:11:34.684Z 52763 TID-owpyjnbbg RepositoryImportWorker JID-9f7f2e565ccda97d3f0b56a5 INFO: start
The authenticity of host 'bitbucket.org (131.103.20.167)' can't be established.
RSA key fingerprint is 97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40.
Are you sure you want to continue connecting (yes/no)? 

I hope this isn't necessary for everyone!

Hmm so we should also manage ~git/.ssh/known_hosts . I am surprised we are not already doing that.

Edit: oh I see @stanhu is using the dev kit.

@stanhu known_hosts is already taken care of in omnibus: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/73f1016fd057a4f146854493a78eba6627c87699/files/gitlab-cookbooks/gitlab/recipes/gitlab-rails.rb#L240

👍

mentioned in issue gitlab-com/support-forum#295 (closed)

Reassigned to @marin

Milestone changed to 8.0

mentioned in merge request !448 (merged)

Status changed to closed by commit 3b0f7ebe