Backport to 17.2: Fixes Geo Replication Details incorrectly empty
requested to merge 468509-backport-to-17-2-fixes-geo-replication-details-incorrectly-empty into 17-2-stable-ee
What does this MR do and why?
Describe in detail what merge request is being backported and why
Backport to 17.2: Fixes Geo Replication Details incorrectly empty !159666 (merged).
There was a merge conflict because in 17.3, find_user_from_job_token_basic_auth
was renamed to find_user_from_job_token_basic_auth_feature_flag_wrapper
and moved.
Original issue: #468509 (closed)
Backport request issue: https://gitlab.com/gitlab-org/release/tasks/-/issues/12629
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). -
This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:package-and-test-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).
Edited by Michael Kozono