Deploy keys after update to gitlab 5.0
Created by: matthee
I recently upgraded from gitlab 4.2 to 5.0 and didn't receive any errors. But while the git commands on my local machine worked fine, i failed to deploy all but one of my projects via capistrano/git to the server, which serves several small rails projects. For all projects i've used the same deployment key. It seems to me, as if only the project, to which i added the key the first time, was able to be deployed.
The first thing i tried to get the deploys working again was to remove and readd the deploy-key of one project, which resulted in a validation error. I tried to fix this by changing the key's comment. While gitlab accepted this key, i still wasn't able to git clone on my production machine.
so i removed the deploy key from all projects using it and added it to only one, and git clone works again like a charm. As you can imagine, it's quite a pain to remove the key from the previouly deployed project and readd the key to the project i currently want to deploy.
so is there currently a working workaround for this issue, because we run several updates a day for different projects?