Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-12998

Separate permission levels for repos in a Mirror farm

XMLWordPrintable

    • 1
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Hey,

      We have started to use the Mirror farms and there is one thing missing to make this even more awesome.

      Use-case: the main purpose for mirror farms in our setup is to remove pressure from our primary instance rather than geographical location.

      This means that a CI/CD environment for a team with a huge repo can hammer on the farm instead of the primary. We now see an extension to this use-case when other teams need to use this repo as well in their CI/CD.

      Even though the huge repo is in the farm these other teams might fetch it from the primary, which takes us back to square 1 to some extent since the farm is "inheriting" the permission setup in the primary.

      Informing the other teams about the existence of the synchronized repo is the obvious way to avoid this but in a rapidly growing org this will be overseen and un-necessary load will be added to the primary instance.

      My suggestion is therefore to add an optional permission level for the Mirror farm for repos that are synchronized. Default value can be to inherit but there should be an option to tweak this to restrict the repo located in the primary to e.g. the owning team only and allow the repo in the Mirror to other teams as well.

      Cheers,

      // Svante

              Unassigned Unassigned
              f9567bb4c8fb Svante Gustafsson
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: