Allow SSH keys to be added to organisations / groups or repos
Description
Currently SSH Keys have to be added to users. This poses a problem for organisations. What if I leave my current job, will they have to scour my account to ensure I don't have any of their server keys loaded against my own account?
Proposal
Organisations should be able to add SSH keys to their servers and add those at an organisational level. This means the keys that are added on servers belong to the organisation, the keys added to laptops etc will belong to the user.
Furthermore added keys to repositories will enable finer grained control. E.g if a server is dedicated to a specific project (repository) then adding that server's key to the repository will prevent code from other repos being pulled down to that server by accident or on purpose.
Links / references
Documentation blurb
Overview
What is it? Allow SSH keys to be added to organisations / groups or repos
Why should someone use this feature? Because SSH Keys can belong to organisations, servers, groups or repos. Not just users.
What is the underlying (business) problem? How do you use this feature?
Use cases
Businesses that have numerous servers each with their own ssh key.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml