azure repo bootstrap failure

[liuzhiyong1982]

After GIT_USER, GIT_TOKEN and GIT_REPO have been set, attempt to run argocd-autopilot repo bootstrap, always get below error:

FATAL unexpected client error: unexpected requesting "https://dev.azure.com/MyADOSubscription/Portal%20Platform/_git/argocd-gitops/git-upload-pack" status code: 400 ; then click the https link, get below error msg: TF401041: The Git protocol sent is not as expected (Unable to read the 4-byte length header of the message.).

Is this a bug?

[noam-codefresh]

sorry, linked to the wrong pr

[liuzhiyong1982]

I still face the same issue with the latest argocd-autopilot binary on v0.3.2.

[naveenkumarsp]

I am also facing the same issue. with v0.3.4

[yanndb]

@noam-codefresh did your incorrect PR go out in release 0.3.2 notes which is leading people to think the bootstrap is fixed, because the PR was for a docker fix

[yanndb]

Just to confirm - v0.3.7, "argocd-autopilot repo bootstrap" fails only if the repo already exists in azure ado. If the repo doesn't exist it can create it fine.
The error:
level=info msg="cloning repo: https://[email protected]/myorg/myproj/_git/argo-starter"
level=fatal msg="unexpected client error: unexpected requesting "https://[email protected]/myorg/myproj/_git/argo-starter/git-upload-pack\" status code: 400"

If I add the --upsert-branch mybranch parameter, it still fails.

Also, after I create a new repo and then try to add a project I equally get a 400 error back because the repo parameter is pointing to a repo that exists.

All same commands work find on github as expected

[avo-sepp]

Hi, I am having the same error right now. Bumping for visibility. v0.4.15

[polinchw]

Hi, I am having the same error right now. Bumping for visibility. v0.4.15

I'm having the same issue.

[AalimahG]

Having the same issue :(
Any update on this ?

[teuferjo]

facing the same issue with v0.4.15

[jblaaa-codes]

using v0.4.17 and running into the same issue with azure devops repo

[krebsmar-materna]

I'm encountering the same error in v0.4.17. Does this mean that ArgoCD AutoPilot is unusable with Azure DevOps?