### Summary This Epics groups all issues that were required for the **replication** of Design Repositories. ### Problem to solve <!-- What problem do we solve? --> Gitlab now supports [Design management](https://docs.gitlab.com/ee/user/project/issues/design_management.html). A first iteration of design repositories that store their files in LFS (https://gitlab.com/gitlab-org/gitlab-ee/issues/9490)is available as of %"12.1"; however, currently these design repositories are not synced via GitLab Geo. This means that large repositories (mainly due to big design assets) can not benefit from Geo replication, and that in a Disaster Recovery situation these data are not available in Geo. Here we propose to sync design repositories using Geo. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> This is relevant for GitLab customers and users who already have a working Geo setup and/or who are considering enabling Geo for either DR or Geo replication features. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> Our customers have a reasonable expectation that new data types being made in Geo in a timely manner. This is a step towards adding another data type and it will bring us close to finishing work on [adding all unreplicated data types](https://gitlab.com/groups/gitlab-org/-/epics/893) ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> Sync design repositories in a similar fashion to wikis or projects. All relevant steps are included in the epic's issues. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> We would need to either add or amend Geo relevant documentation. ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> The testing requirements are similar to other data type. ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> * Design repositories are synced to Geo secondaries in a similar way to wikis.