You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently attempting to run Cerbos using the git driver but are running into an issue with our repositories. We use Azure DevOps which does not fully support the git protocols being used (apparently after some searching around). Attempted both SSH and HTTPS.
2022-10-14T17:21:31.831Z INFO cerbos.server maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined
2022-10-14T17:21:31.831Z INFO cerbos.server Loading configuration from /config/config.yaml
2022-10-14T17:21:31.838Z INFO cerbos.git.store Cloning git repo from {{REPO}} {"dir": "/work"}
2022-10-14T17:21:33.029Z ERROR cerbos.git.store Failed to initialize git store {"dir": "/work", "error": "failed to clone from {{REPO}} to /work: empty git-upload-pack given"}
2022-10-14T17:21:33.029Z INFO cerbos.server maxprocs: No GOMAXPROCS change to reset
cerbos: error: failed to create store: failed to clone from {{REPO}} to /work: empty git-upload-pack given
A lot of the issues are really old and its most likely an Azure DevOps failing but just bringing this up in case there is any workaround or ability to use it for Azure DevOps.
The text was updated successfully, but these errors were encountered:
Thanks for reporting the issue. We haven't tested Cerbos with Azure DevOps but based on the comments by other go-git users and the upstream issues that you've already found, I suspect the issue is in the git library rather than Cerbos itself.
Unfortunately, I don't have a workaround for you at the moment (unless you would like to try one of the other storage mechanisms supported by Cerbos). We've run into several other issues with the go-git library and want to replace it but it will take some time.
A lot of the issues are really old and its most likely an Azure DevOps failing but just bringing this up in case there is any workaround or ability to use it for Azure DevOps.
We actually went the same approach with kubernetes git-sync init container on Deployment creation, then a side-car of it constantly polling our git and cerbos just pointing to the volume it sync'd too. Working pretty well.
We are currently attempting to run Cerbos using the git driver but are running into an issue with our repositories. We use Azure DevOps which does not fully support the git protocols being used (apparently after some searching around). Attempted both SSH and HTTPS.
go-git/go-git#64
src-d/go-git#335
A lot of the issues are really old and its most likely an Azure DevOps failing but just bringing this up in case there is any workaround or ability to use it for Azure DevOps.
The text was updated successfully, but these errors were encountered: