Generate a deploy key per repo in the Git extension
Currently, the Git extension only generates one deploy key per Plesk user (according to @PleskHelps on Twitter). Unfortunately, GitHub doesn't allow a deploy key to be used more than one time across ALL repos, meaning every single GitHub repo requires a unique deploy key. As a result, I can clone only one of the 40 some repos I would like to on my Plesk installation.
I would like to suggest the option to have a unique deploy key generated for every single repo you want to clone. That would make the Git extension infinitely more useful for me and many others, especially when using Github as the upstream master for them.
This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!
Otoniel Guajardo commented
WE NEED THIS!
Erik Kraijenoord commented
Same issue here, subdomains within same service are different repositories but we cannot connect through SSH because Plesk only authenticates for one SSH key.
Required update on this issue thanks!
No updates for a year? This absolutely needs to be addressed. This is a very significant functionality flaw.
Any update on that?
Robert Green commented
This is an absolute must! I have a app with different sub-domains and each with its own repo... Having this is kind of like CI/CD within TFS. I hope that you all get this resolved ASAP!
Joe Toscano commented
This still hasn't been addressed? What's the deal? I have 6 dev site subdomains for my company's clients that I would like to hook private repos up to... but I can't...
Agreed... a must addition!
Colin Brady commented
Agreed! This would be very helpful.
Bramus Van Damme commented
Just ran into the same issue today. Indeed a big miss in the extension.
Zachary Skaggs commented
Can anyone acknowledge this please? This is a pretty big miss in this extension.