Move GitLab V1 Import Repository Route to the New Router
Context
See parent epic.
Solution
Since this is the first route that we're implementing in the new router, we'll need to do a fair bit more work compared to the following routes. Most of these tasks are small enough to be covered by this issue, namely these are:
-
Add (temporary) visibility for which router is being used for each request. -
Implement the base V1 route in Chi -
Ensure relative URLs are functionally equivalent between gorilla and chi -
Ensure host ULRs are functionally equivalent between gorilla and chi -
Ensure the http prefix configuration produces ULRs that are functionally equivalent between gorilla and chi -
Implement the GitLab V1 Import Repository Route in Chi -
Ensure arbitrary length repository names are functionally equivalent between gorilla and chi -
Use the Chi route for the GitLab V1 Import Repository Route in the URL builder -
Serve the GitLab V1 Import Repository Route with Chi
Edited by Hayley Swimelar