Allow non-development environments to perform local project imports
!135681 (merged) introduced a change that made local and link-local project imports configurable by the application settings, while limiting them to development environments.
However, there is a use case for importing from instances on the same subnet in production use-cases (self-managed customers migrating from other self-managed instances) so we need to remove the development env requirement.
Affected customers:
- https://gitlab.com/gitlab-com/dev-sub-department/section-dev-request-for-help/-/issues/197
- https://gitlab.com/gitlab-com/dev-sub-department/section-dev-request-for-help/-/issues/201
- https://gitlab.com/gitlab-com/dev-sub-department/section-dev-request-for-help/-/issues/203
Unexpected Behavior
People impacted by this problem see the Requests to the local network are not allowed
error when attempting to import from a host that is not on the local network.
Workaround
It is possible to work around this problem by adding the FQDN for the host you are importing from to the the allowlist in GitLab under Settings > Network > Outbound requests.
Several customers impacted by this problem have reported that this workaround works. GitLab team members with access to Zendesk can learn more in the tickets: 1 2.