Details
-
Suggestion
-
Resolution: Won't Fix
Description
Scenario
A Bitbucket Team or Account has multiple repositories (sometimes dozens) that have dependencies on other repositories under the same Team/Account and needs to pull other repositories during the pipelines steps.
Current Solution
In order for repo-a to pull repo-b that is under the same Team/Account, an admin must manually go into repo-a and copy the public key then go into repo-b and add that public sshkey as an “Access Key”.
Proposed Enhancement
All repos under a Team/Account should have an option to automatically manage this process of sshkey/access key to sibling repos. The manual process of going through (potentially dozens) of repos to add access keys to accomplish this process is tedious and requires more overhead then necessary and should be automated or configurable in the Repo or Team/Account configs.