Skip to content

fix: some self-managed GitLab deployments not handling project URLs

Tomas Vik requested to merge 143-get-project-through-graphql into main

This is completely working around #143 (closed).

TLDR; Apache and other proxies are not compatible with parts of the GitLab REST API projects endpoint. More info in this comment: #143 (comment 384935174)

We knew about the upstream issue gitlab#18775 (closed) and closed #143 (closed) because it's not, strictly speaking, caused by the extension. But the extension users hit this proxy issue quite often. Just helping users resolve the bug reports was taking too much time compared to implementing this workaround.

The workaround

Instead of making a REST API request like: https://gitlab.com/api/v4/projects/gitlab-org%2Fgitlab-vscode-extension we make a GraphQL request like:

query GetProject{
  project(fullPath: "gitlab-org/gitlab-vscode-extension") {
    id
    name
    fullPath
    group{
      id
    }
  }
}

This completely avoids the problem with having to escape the fullPath.

Related to #143 (closed)

Edited by Tomas Vik

Merge request reports