Add merge_request_refs_cleanup feature flag
What does this MR do?
We are experiencing performance issues with the merge request refs cleanup functionality on production and some customers instances. This became more visible when we started backfilling MergeRequest::CleanupSchedule records for old merge requests.
Disabling the worker and scheduler for now behind a feature flag so we can test the feature once we improve it's scheduling logic before enabling it on other instances.
The scheduler is currently disabled on GitLab.com via a kubernetes config change in gitlab-com/gl-infra/k8s-workloads/gitlab-com!621 (merged).
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team