4
Git Sync: Azure DevOps repositories fail with 404 because nanogit unconditionally appends .git to URLs
Source: grafana/grafana#120149 · opened by @MikeDevresse
What happened? Configuring the Grafana 12 git sync feature (Administration → Provisioning) with an Azure DevOps repository fails with: failed check if authorized: get repository info: got status code 404: 404 Not Found The root cause is that nanogit (v0.3.0) unconditionally appends [.git](vscode-file://vscode-app/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/workbench.html) to every repository URL, regardless of whether the server supports it. Azure DevOps interprets [.git](vscode-file://vscode-app/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/workbench.html) as a literal part of the repository name (not a suffix to strip), so the resulting URL points to a non-existent repository. In [email protected]/rawclient.go: This transforms: to And azure devops doesn't support .git extensions What did you expect to happen? Grafana connects successfully to the Azure DevOps repository using the provided URL and PAT. Did this work before? N…
No pledges yet. Be the first to back this.
Comments
Similar requests
Git Sync: Support Azure DevOps repositories with Microsoft Entra Managed Identity authentication
4 votes · 0 comments
git-sync: "uid too long" when git-sync a dashboard with a long metadata.name
0 votes · 0 comments
Git Sync: optional enforcement mode — make the repository the only write path when `sync.target: instance`
2 votes · 0 comments
Azure: Resource picker E2E test improvements
0 votes · 0 comments
Git Sync Support for Github Enterprise on Grafana OSS
0 votes · 0 comments
No comments yet.