Resolve "Geo: enable housekeeping functionality when syncing repositories"
What does this MR do?
Adds automatic housekeeping functionality to Geo synced repositories, following same logic as per-push housekeeping.
Are there points in the code the reviewer needs to double check?
We are re-using all thresholds from the per-push housekeeping. We also are re-using the toogle to enable/disable housekeeping per push here. The rationality is that, if it's disable on primary, we should respect that and vice versa.
Why was this MR needed?
Geo secondary currently has no automated way to perform housekeeping into repositories.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Tests added for this feature/bug - Review
-
Has been reviewed by Backend
-
-
EE specific content should be in the top level /ee
folder -
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
End-to-end tests pass ( package-qa
manual pipeline job)
What are the relevant issue numbers?
Closes #5717 (closed)
Edited by Gabriel Mazetto