-
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
optional property does not work with azure artifacts #11179
Comments
Hey @liangyuanpeng, thanks for fixing it. Just wanted to confirm when can we expect the fix to release? |
Had to retrigger the CI. Once it’s merged, you can try it in the latest image tag. |
terrytangyuan
pushed a commit
that referenced
this issue
Jul 1, 2023
Signed-off-by: Lan Liang <[email protected]>
JPZ13
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jul 4, 2023
…oproj#11235) Signed-off-by: Lan Liang <[email protected]>
61 tasks
terrytangyuan
pushed a commit
that referenced
this issue
Jul 19, 2023
Signed-off-by: Lan Liang <[email protected]>
dpadhiar
pushed a commit
to dpadhiar/argo-workflows
that referenced
this issue
May 9, 2024
…oproj#11235) Signed-off-by: Lan Liang <[email protected]> Signed-off-by: Dillen Padhiar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
Expected behaviour -
When optional is set to true then the workflow shouldn't error out even if the azure artifact isn't present.
Actual behaviour -
In case of azure artifact this doesn’t work as intended. I tried setting optional to true for an input artifact when the file is not present, it threw an error.
Error message -
Error (exit code 1): artifact file failed to load: unable to download blob test-artifact/s3-artifact/no-file.txt: ===== RESPONSE ERROR (ErrorCode=BlobNotFound) ===== Description=, Details: (none)
This works in case of s3 artifacts, when I set it to true and the file is not present it does not throw an error. (expected behaviour)
Version
v3.4.7
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.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: