Open sakvaka opened 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions.
Pre-requisites
:latest
What happened/what you expected to happen?
Since S3 artifacts cannot be parsed directly from URI (see https://github.com/argoproj/argo-workflows/issues/4349), I need to extract the
bucket
andkey
parts from the URI. I tried usingsprig.splitList
to split the URI at / symbols, and slice the list to get the bucket and key components. Then, I use the third component as the bucket name and withsprig.join
, I join the other parts but the first three to get the s3 key part.However, this string handling seems to work when defining parameters but not when defining an s3 artifact key. Submitting the workflow below gives a validation error
Bad Request: templates.starthere.steps[0].main templates.main.steps[2].consume.arguments.file.from, artifact location, or key is required
. The error may be related to the list slicing part ([3:]
), since removing the slicing makes the validation error message disappear. Surprisingly, the same slicing is handled correctly with thebucket:
specification, which is however without thesprig.join
.The
whalesay
templates are in the following workflow just to demonstrate there is no syntax error in the variable expressions.Version
V3.4.6
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