Fix api Geo spec
What does this MR do?
Fixes https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/47626105 happening on EE master.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
What are the relevant issue numbers?
Merge request reports
Activity
assigned to @ClemMakesApps
cc @digitalmoksha I think our changes conflicted (but I guess didn't conflict according to git merge)
enabled an automatic merge when the pipeline for fa48635f succeeds
changed milestone to %10.5
added typebug label
mentioned in commit a9521a83
mentioned in commit f433adcd
@mkozono sorry about that if I caused it. Thanks for taking care of it :-)
@digitalmoksha Nope, not your fault-- it was a logical conflict that didn't generate a merge conflict. Just wanted you to see it bc this is not unusual esp with lots of concurrent work in Geo.
Picked into https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4148, will merge into
10-4-stable-eeready for10.4 RC8 EEmentioned in commit 376125be
added devopssystems groupgeo labels
added Enterprise Edition label
