Geo - HTTP - clone/pull: Redirect to Primary when selective sync enabled and project not selected for sync or not yet sync'd

Problem to solve

When performing:

• git clone/pull operations
• on a Geo secondary
• via HTTP
• where selective sync is enabled

and a given project is either not selected for sync or has not yet sync'd, the user will receive an error.

Proposal

Instead of returning an error, we should detect the scenario outlined above and redirect to the Geo Primary to fulfil the request. We should also advise the user what is happening via a useful terminal message such as:

> You attempted to access X via a local Geo secondary but the project is currently not replicated
> You are being redirected to the primary node X
> Please contact your systems administrator to ensure all relevant projects are replicated to your closest Geo node.

Related: &2562 (closed)