-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Authentication issue on Azure devops with the git artifact example #11705
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Hi @agilgur5 thank you for marking this as a bug. Do you have news on this issue? |
No. Any updates would be in the issue. Please see https://sindresorhus.com/blog/issue-bumping. You also did not fill out the bug report template, which does not help.
The fix to #10600, #10953, was not released until 3.5.0-rc1. So I would suggest trying with 3.5.0 |
you are right @agilgur5 , let me provide more information Pre-requisites
What happened/what you expected to happen? Version
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images. apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: input-artifact-git-
spec:
entrypoint: git-clone
templates:
- name: git-clone
inputs:
artifacts:
- name: argo-source
path: /src
git:
repo: https://dev.azure.com/<projectFolder>/_git/<repoName>
branch: main
usernameSecret:
name: azuredevops-git-secret
key: username
passwordSecret:
name: azuredevops-git-secret
key: password
container:
image: golang:1.10
command: [sh, -c]
args: ["git status && ls && cat VERSION"]
workingDir: /src The secret was created with apiVersion: v1
data:
password: <password>
username: YXJnbw==
kind: Secret
metadata:
name: azuredevops-git-secret
namespace: argo
type: Opaque Logs from the workflow controller
Logs from in your workflow's init container
I hope this is enough to understand the issue. Thanks |
Thanks for the update @mfabbri. Could you please add code blocks and syntax highlighting (i.e. ```yaml) to your comment? It looks like it wasn't formatted correctly. So you're still having this issue in 3.5 then, correct? |
You're right @agilgur5 : I didn't remember the syntax. Now it's fixed. Please @rohankmr414 , ask me any additional details you need about the test I performed. Thank you both |
I think I might have found the issue. #10953 merely bumped That should be fairly simple to add. @mfabbri would you be interested in contributing that? If not, I can probably take this on |
Thank you for the proposal @agilgur5 but I don't think I have enough knowledge to proceed with this implementation. Can you take it? |
Signed-off-by: Christian Lütke Stetzkamp <[email protected]>
Signed-off-by: Christian Lütke Stetzkamp <[email protected]>
Signed-off-by: Christian Lütke Stetzkamp <[email protected]>
Signed-off-by: Christian Lütke Stetzkamp <[email protected]>
Hi all,
the issue 10600 is closed but I still have an authentication issue on Azure devops with the git artifact example
https://github.com/argoproj/argo-workflows/blob/master/examples/input-artifact-git.yaml
artifact argo-source failed to load: failed to clone "https://<org>@dev.azure.com/<org>/folder/_git/customerdata": unexpected client error: unexpected requesting "https://<org>@dev.azure.com/<org>/folder/_git/customerdata/git-upload-pack" status code: 400
This error is thrown using Argo Workflow 3.4.10: any idea?
Thanks
Originally posted by @MarcoFabbri-orienteed in #10600 (comment)
The text was updated successfully, but these errors were encountered: