Remove legacy design repo replication
What does this MR do and why?
Remove legacy design repo replication and geo_replication API since these features are now supported by Geo's self-service framework.
Unused table for design_registry
will be dropped in a follow-up MR !126132 (merged)
Related issue: #391189 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
- Setup Geo
- add a new issue with designs to a project
- check if it replicates and verifies on /admin/geo/sites
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Aakriti Gupta