Improve Deploy Key Management
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Zendesk issue: https://gitlab.zendesk.com/agent/tickets/25410
Deploy keys are often difficult to work with because you cannot add the same key twice. If you are the person the adds the key then you can see the key on other projects and enable it there, too. However, if you're not the one that added it, and don't have master/owner access to that particular project, you will be unable to see and enable that key elsewhere.
We now have a global deploy key management page in the Admin area, but that's not enough. How can we improve the process of finding and adding other deploy keys? There's not really a security risk associated with showing all keys publicly. However, how would we allow users to search and find the right one among thousands?
I'm assuming we cannot allow duplicate keys because it would not work in the authorized_keys file? Any ideas how to make this better?
cc/ @DouweM @rspeicher This is a pretty complex question. Do you have any ideas how to improve deploy key use?