Send relative path header to Gitaly
What does this MR do and why?
Gitaly sends the relative path of the repository to the
internal/allowed/
GitLab API endpoint so access checks can support
reading objects that exist within snapshot repositories. For Gitaly to
provide access to snapshot repository objects, the repository relative
path must be propagated back to Gitaly in subsequent RPCs invoked as
part of the access checks.
Send the repository relative path as an HTTP header during Gitaly RPCs used for access checks.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.