import.git
unable to import from Azure DevOps Repository
#2924
Labels
bug
Something isn't working
documentation
Improvements or additions to documentation
type/docs
Docs Squad label across all Grafana Labs repos
What's wrong?
While building an Alloy configuration which needs to get a custom component from an Azure DevOps repository, I was unable to successfully retrieve the custom component via the
import.git
component, despite being authorized correctly.Having dug a few resources, I learnt that the git implementation used by Alloy (namely go-git) had some issues with implementing multi_ack which is leveraged by Azure DevOps repositories This was discussed in go-git issue 64. The subject is beyond my area of expertise, but given that go-git contributors implemented a fix with the following caveats tells me that services using go-git need to go through a few extra hurdles to work well with repositories leveraging multi_ack.
@dehaansa was kind enough to share an alternative approach using
import.http
instead which worked like a charm using Azure's APIs to get the file from the repository via REST as seen below:(important to use
tfsgit
as a source provider due to this issue with the API.)But....it would be nice if this issue is addressed for us ADO users! Should definitely be noted in the documentation as well as it would save people a lot of head scratching!
Steps to reproduce
System information
Docker WSL (Ubuntu)
Software version
v1.7.1
Configuration
Logs
The text was updated successfully, but these errors were encountered: