Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git driver does not support Azure DevOps Repositories #1279

Open
Greg15153 opened this issue Oct 14, 2022 · 4 comments
Open

Git driver does not support Azure DevOps Repositories #1279

Greg15153 opened this issue Oct 14, 2022 · 4 comments
Labels
future-work Something considered for future relases kind/bug Something isn't working

Comments

@Greg15153
Copy link

Greg15153 commented Oct 14, 2022

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

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.

@charithe
Copy link
Contributor

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.

@charithe charithe added kind/bug Something isn't working future-work Something considered for future relases labels Oct 14, 2022
@Greg15153
Copy link
Author

Thanks for the quick feedback. We'll be exploring the other options to see how well they work for us.

@mattduguid
Copy link

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.

@Greg15153 workaround for azure devops git repos -> GoogleContainerTools/kaniko#719 (comment)

@Greg15153
Copy link
Author

Greg15153 commented Nov 17, 2022

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.

https://github.com/kubernetes/git-sync

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future-work Something considered for future relases kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants