There should be a way to apply a deploy key to many repos at one time.
This would be amazing.
Issue #5879 was marked as a duplicate of this issue.
Issue #5945 was marked as a duplicate of this issue.
This. Would. Be. Huge.
I was just trying to figure out this exact issue. Larger projects with subrepos really amplify this issue as well.
It would actually be quite nice if the deploy key interface worked like the user interface letting me create groups and each group has keys in it etc. Alternately letting a group admin create deployment "users" that can be added to the regular user groups would also work fine.
Sean Head exactly +1
Marko Žmak - Žmale
+1000 from me
Nguyen Thanh Trung
Toni Van de Voorde
+1 (Or at least provide a work around)
Daniel BennettAccount Deactivated
Issue #8433 was marked as a duplicate of this issue.
Would love this! Especially with different composer packages and repos this is basicly a must have.
I'm currently setting up our QA & production servers to use deployment keys for each of our several code repositories. This feature would be awesome right about now.
This has been open for 3 years now... will there be fix for this?
I'd like a fix for this since multiple projects can be deployed on the same server, but we cannot use the same deployement key... it's a pain in the a**!
But again it's a wonderfull feature that would be too good for us, so Atlassian are stalling again! Days like today I regret moving to bitbucket!
any update on this ?
Ivan de Queiroz
How about to apply a deploy key to a team? All repositores owned by the team will be covered at once.
@mbertrand80 any change this will be worked on ?
Update: I believe this is already working . I just upgraded my plan from the free 5 person plan to 10 and now on my manage team page i see an option to set an SSH Key. I remove the one i set on all my individual repos , moved it to here and everything seems to work fine!
Strange that this ticket would stay open for 3 years ...
It works for teams, but not for the real subject of the ticket and I don't want to make a read only team for each server that I want to deploy to.
I just smile looking how Atlassian team ignore just every important ticket for years without even commenting it.
Checking the team settings, it has the SSH Key feature, but it is read-and-write. Just want the read privilege.
Really guys? 3 years?
There is, but it requires setting up an associated account as a deployment entity, and giving it keys. If you use the same email when setting up the account, it does notice it's you.
This is pretty bad. The only solution is to add it to the company SSH key section - which means you can't restrict certain servers to certain repos.
So either I do a global read/write access (bad).
Or I have to go to each individual repo and add deployment keys.
Gitlab does this way better - just have a "Manage Deployment Keys" page where you can paste keys and choose which repos it has "Read" access to.
@mbertrand80 Are there plans to add deployment keys for teams or is there another workaround than adding deployment keys for every project?
I had been using the team account credentials to read source into our build server (Jenkins) but wanted to change the password. Couldn't find any mention of it on the site so raised a ticket, to be told team accounts aren't allowed anymore and sent me to this ticket. Seems the only work around is to create a "team user" that can read the source, but that blows one of my development slots.
What's wrong with having a read only team login, for build servers?
really bad to miss this feature... adding/managing read-only deploy keys on dozens of repos currently causes a huge workload. Should not be hard to implement at all.