Move project repository storage classes to namespace
What does this MR do?
This MR is needed to keep the code aligned. According to our guidelines and cops (!51236 (merged)), classes should be namespaced. Related to the repository storage update, we introduced the new classes for groups in a namespace, but there are others, for projects and snippets, that still follow the old naming. So now, we have mixed namespaces in this functionality.
With this MR we start cleaning that up and move everything to a namespace.
Since some of the classes are workers or called inside existing workers, we cannot get rid entirely of these classes, and we need to wait for 14.0 to do that.
In specific we do:
- Move
ProjectRepositoryStorageMoves
entity toProjects::RepositoryStorageMoves
- Copy
ProjectRepositoryStorageMoves
model toProjectsRepositoryStorageMoves
- Remove all the logic from
ProjectRepositoryStorageMoves
- Make
ProjectRepositoryStorageMoves
a subclass ofProjects::RepositoryStorageMoves
- Remove all the logic from
- Copy
ProjectUpdateRepositoryStorageWorker
toProjects::UpdateRepositoryStorageWorker
- Remove all the logic from
ProjectUpdateRepositoryStorageWorker
- Make
ProjectUpdateRepositoryStorageWorker
a subclass ofProjects::UpdateRepositoryStorageWorker
- Remove all the logic from
- Copy
ProjectScheduleBulkRepositoryShardMovesWorker
toProjects::ScheduleBulkRepositoryShardMovesWorker
- Remove all the logic from
ProjectScheduleBulkRepositoryShardMovesWorker
- Make
ProjectScheduleBulkRepositoryShardMovesWorker
a subclass ofProjects::ScheduleBulkRepositoryShardMovesWorker
- Remove all the logic from
- Replace all references to the old classes with the new ones.
Does this MR meet the acceptance criteria?
Conformity
-
Code review guidelines -
Merge request performance guidelines -
Style guides -
Separation of EE specific content
Related to #299853 (closed)
Edited by Francisco Javier López (ex-Gitlab)