Auto DevOps: SSH key integration
Problem to solve
SSH keys are not supported in Auto DevOps as well as in GitLab CI/CD, so Auto DevOps is not automatic when the repo requires SSH keys to build (internal submodules, private packages using your package manager etc.).
Delaney, Development Team Lead, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#delaney-development-team-lead
Sasha, Software Developer, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#sasha-software-developer
Developers must prepare SSH keys that are required for internal submodules, private packages using your package manager even when Auto DevOps is used by following Using SSH keys with GitLab CI/CD.
When developers add their SSH keys though Variables Web UI or Variables API, these SSH keys are deployed in GitLab Runner environment. UI for adding/editing/deleting SSH keys can be specific instead of general variables.
Permissions and Security
Project developer+ can create/edit/delete configuration of this SSH key integration. Group-level configuration is a nice-to-have.
What does success look like, and how can we measure that?
https://docs.gitlab.com/ee/ci/ssh_keys/ would have less its page views as developers would not have to setup SSH keys on Auto DevOps use.