Geo: Implement async Geo Proxy API calls
What does this MR do?
Make calls to /api/v4/geo/proxy
asynchronously, once every 10 seconds.
Resolves #329671 (closed)
Description | Issue | MR(s) |
---|---|---|
Add endpoint /api/v4/geo/proxy
|
#324664 (closed) | !63343 (merged) |
Determine if this is a Geo Proxy by calling /api/v4/geo/proxy
|
#329670 (closed) | !60769 (merged) |
If this is a Geo Proxy, then use the Geo Proxy routing table | #329672 (closed) | !63321 (merged) |
Cache the result of the request | #329671 (closed) | !66491 (merged) You are here |
[Feature flag] Rollout of geo_secondary_proxy and GEO_SECONDARY_PROXY
|
#325732 (closed) |
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) => Not needed. The API endpoint is feature flagged, and the major workhorse changes are behind environment variable as well. -
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.)
Edited by Michael Kozono