-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
Feature Overview
- When a customer uses Gitlab's Geo feature and ArgoCD is pointing to a secondary instance, if the secondary instance is not synced, it redirects the pull requests, and ArgoCD cannot handle it, failing. There should be a configuration to allow redirects.
Business Goal/Objective
- What is the Business Goal/Objective of this outcome?
Being compatible with the Gitlab's HA solution