Attempting to use the GitLab PHP storm plugin (makes request as part of setup and normal operations) and the GitBlur app make requests to the issues endpoints.
See:
https://docs.gitlab.com/ee/api/issues.html
https://docs.gitlab.com/ee/api/epic_issues.html
While we are not using issues yet I see little harm in allowing access to this endpoint, especially for GET requests. Eventually we will need this open and for now it will just return empty results which will keep the API clients happy.
It may be worth opening for POST as well since this will eventually be wanted once issues are migrated to G.D.O and users can not create issues on projects where issues are disabled so again no harm in allowing.
Already documented in GitLab documentation:
curl --header "PRIVATE-TOKEN: your_access_token" "https://git.drupalcode.orgapi/v4/issues"
Allow the Issues endpoint
Modify CDN access rules
Fixed
GitLab
Adding a tag to track requests related to the GitLab API
We are no longer stripping authentication headers for GET & HEAD requests to GitLab’s REST API, so authenticated reads are generally supported.
Automatically closed - issue fixed for 2 weeks with no activity.