-
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
sprig expression that works in 3.3.9 doesn't work in 3.4.0 #9625
Comments
Not sure, but I assigned it to myself so I can take a look. |
@tooptoop4 since your regex example is finding some text like "landing/" I thought I might see that in your example payload, but it isn't in there, right? Do you by chance have a payload that better matches the nested regex expressions? |
@juliev0 in the json payload u can change po_235248_pan_0000000.ntf to landing/mysch/mytbl/po_235248_pan_0000000.ntf |
okay, thanks! |
I can see that the commit you referenced does in fact break this. And that's because in operator.go, substituteGlobalVariables() is now being called after updateWorkflowMetadata(). I need to do more investigation to figure out the right order for these functions to be called. I believe in that commit that the order got changed, but for a different reason. |
Pre-requisites
:latest
What happened/what you expected to happen?
a param to my workflow is a payload like the json in these 12 lines:
https://github.com/LeidosLabs/holeshot/blob/b3aa04a84059e3a4c07d42ff9a46cc37f443eb3d/ingest-service/src/test/resources/sample-notification.json#L1-L12
my expression below worked fine in 3.3.9 but in 3.4.0 gives error
Version
3.4.0
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.
n/a
Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}
Logs from in your workflow's wait container
kubectl logs -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
The text was updated successfully, but these errors were encountered: