Draft: Draft: Rename Geo::DesignRegistry to Geo::DesignRepositoryRegistry for consistency
What does this MR do and why?
With the introduction of the Projects::DesignRepository
model in !108530 (closed), we want to make the naming for design repo replication consistent throughout the code.
Except for changing the name of the geo_design_replication
feature flag and the name of the table design_registry
, all other uses have been edited.
This is in preparation for migrating Design repo replciation and verification to Geo's self-service framework in #355660 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
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.