Cloning with git-fallback-clone seems to fail

[ckotzbauer]

Cloning with git-fallback-clone seems to fail

[ckotzbauer]

Hi @GDWBaer,
can you please share your config (helm-chart values or deployment.yaml) that I can see the parameter you added?

[GDWBaer]

Sorry for replying late. I overlooked the info mail. My values.yaml file looks like:
`image:
tag: "0.17.0"

args:
targets: git
format: cyclonedxjson
git-author-email: ************************************
git-author-name: ""
git-repository: https://@dev.azure.com///_git/*************************
git-branch: "sbom-operator"
git-path: aks/sbom
git-fallback-clone:
git-workingtree: /work/sbom
#git-username: "******"
#git-password: ""
git-access-token: ""
verbosity: debug

#envVars:

- name: SBOM_GIT_ACCESS_TOKEN

valueFrom:

secretKeyRef:

name: "sbom-operator"

key: "accessToken"`

I played around with setting the access token by parameter and from kubernetes secret...

[GDWBaer]

Maybe an image is easier to read here:

[ckotzbauer]

Thanks, I will have a look at this on the weekend

[ckotzbauer]

I could reproduce the issue: The problem was, that the repo or branch was empty. The operator assumes a fully initialized repository/branch to work on. There's no logic which creates the specified branch if it does not exist. Please commit a README or something else to the branch. I will add this requirement to the docs.

Feel free to reply here, if this doesn't work.

[GDWBaer]

Hi Christian, the branch is definitely existing in the origin. Do you see a way of getting the complete error message git is throwing? It seems to be only a stub (1st line?) for me:
time="2022-09-28T07:45:05Z" level=error msg="Open or clone failed" error="'git clone -b sbomtest https://dev.azure.com/******/*****************/_git/******************** /work' failed: Cloning into '/work'..."
When I log into the container I can successfully clone the repo to an empty destination:

The original destination is not empty anymore because the sbom-operator starts to create sboms even after the clone failed.

[ckotzbauer]

I added the exit-code from the git-command to the error-message in the newest release. The stderr message from the command is logged, so it seems that git doesn't emit an error-message. @GDWBaer

[acook8]

@GDWBaer I was having the same issue with Azure DevOps. What I did to get it to work was set SBOM_GIT_REPOSITORY to https://{pat}@dev.azure.com/{organization}/{project}/_git/{repo}

[GDWBaer]

@GDWBaer I was having the same issue with Azure DevOps. What I did to get it to work was set SBOM_GIT_REPOSITORY to https://{pat}@dev.azure.com/{organization}/{project}/_git/{repo}

Hi, thanks for the hint. Could you give a more complete example? Is this env var the only config you used? Is the {pat} raw or base64 encoded? I tried with a raw token without luck, yet.

[acook8]

Hi, thanks for the hint. Could you give a more complete example? Is this env var the only config you used? Is the {pat} raw or base64 encoded? I tried with a raw token without luck, yet.

The PAT I used was not encoded. The arguments I have set are:

• git-author-email
• git-author-name
• git-username
• git-path
• git-fallback-clone

And I have these environment variables:

• SBOM_GIT_PASSWORD
• SBOM_GIT_REPOSITORY

I probably don't need all of those set, but I haven't gone back and cleaned up anything that isn't needed

[ckotzbauer]

Hey @acook8, @GDWBaer,
I just pushed ghcr.io/ckotzbauer/sbom-operator:0.23.0-beta.1 (hopefully 0.23.0 later today) with go-git 5.5.0 built-in. This release added support for multi_ack. I justed tested a private Azure DevOps repo with this release without the --git-fallback-clone flag and it worked. Could you please have a look and give me a quick hint if this works for you?
If yes, I will remove the fallback-clone in the near future.

I tested with this URL-format and username and password (as flags): https://{organization}@dev.azure.com/{organization}/{project}/_git/{repo}

[ckotzbauer]

Closing this for now. Please respond if there are still errors.