Manage read access for dependent repos without managing SSH keys

Currently, for repo A that clones repo B in Bitbucket as a dependency, an admin must

• A pipeline SSH key pair must be generated
• The public key generated must be added as an read-only access key to the dependent repo

This must be repeated for each repo and dependent repo.

Feedback received on the https://confluence.atlassian.com/display/BITBUCKET/Use+SSH+keys+in+Bitbucket+Pipelines page:

"Can you simplify this for us and just add a dropdown list with all the other Bitbucket repositories (accessed by the repo admin) and manage SSH access to them for Bitbucket Pipelines seamlessly? I just want to choose on a repo A that it's pipelines should have access to a repo B and not spend hours troubleshooting SSH keys. I bet you think it's easy and you know how to do it, but for me it's unnecessary blocker and it just doesn't work."