argocd-autopilot azure repo bootstrap failure

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?

Apr 03 '22 07:04 liuzhiyong1982

sorry, linked to the wrong pr

Apr 08 '22 20:04 noam-codefresh

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

Apr 13 '22 03:04 liuzhiyong1982

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

Apr 27 '22 15:04 naveenkumarsp

@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

May 25 '22 16:05 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

May 26 '22 07:05 yanndb

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