Support repository moved message with all container types
What does this MR do?
Rename the ProjectMoved
push check to ContainerMoved
, and use the
repository identifier to store messages in Redis instead of the project
ID.
Previously this only worked in a project context, but now supports all repository containers and also adds the container type in the push message.
To handle the transition from the previous message key to the new one, we query and delete both keys in Redis.
Implements #292030 (closed)
QA
To test locally:
- Create a project/snippet/wiki and clone it locally.
- Change the path of the project/group (this is not possible for personal snippets).
- Go to Settings -> General -> Advanced -> Change path / Change group URL
- Create a commit locally and push it.
Group wiki:
Project repository:
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) - [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
-
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) - [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
-
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) - [-] I have tested this MR in all supported browsers, or it's not needed.
- [-] I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Related to #207869 (closed)
Edited by Markus Koller