-
Notifications
You must be signed in to change notification settings - Fork 3.4k
fix: Fixes parameterized global artifacts resolution in exit handlers. Fixes #11610 #14991
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
fix: Fixes parameterized global artifacts resolution in exit handlers. Fixes #11610 #14991
Conversation
Signed-off-by: ItielOlenick <[email protected]>
afd1f36 to
6e27ca6
Compare
…n-in-exit-handler
…n-in-exit-handler
|
Hey @ItielOlenick, I was looking to review this as I recently fixed a similar issue in #15033. As part of that I refactored the It looks like you'd just need to ensure your code commented with if strings.HasPrefix(variable, "workflow.outputs.") {
continue
}part and from |
…n-in-exit-handler Signed-off-by: ItielOlenick <[email protected]>
Signed-off-by: ItielOlenick <[email protected]>
|
@elliotgunton After taking a look at your changes and doing some more testing, I removed all of the expression related changes as they seemed unnecessary and left only the validation ones. |
…n-in-exit-handler
elliotgunton
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
|
Whilst testing this I've noticed a couple of things - I'll also take the test from #11610 and turn it into an e2e test |
|
❌ Cherry-pick failed for 3.7. Please check the workflow logs for details. |
|
❌ Cherry-pick failed for 3.6. Please check the workflow logs for details. |
Signed-off-by: Alan Clucas <[email protected]>
…Fixes #11610 (#14991) (cherry picked from commit 199a137) Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: Alan Clucas <[email protected]>
…Fixes #11610 (#14991) (cherry picked from commit 199a137) Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: Alan Clucas <[email protected]>
Signed-off-by: Alan Clucas <[email protected]>
…Fixes argoproj#11610 (cherry-pick argoproj#14991 for 3.7) (argoproj#15056) Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: Alan Clucas <[email protected]> Co-authored-by: ItielOlenick <[email protected]>
…Fixes argoproj#11610 (cherry-pick argoproj#14991 for 3.6) (argoproj#15057) Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: Alan Clucas <[email protected]> Co-authored-by: ItielOlenick <[email protected]>
…Fixes argoproj#11610 (argoproj#14991) Signed-off-by: ItielOlenick <[email protected]> Signed-off-by: ItielOlenick <[email protected]>
Signed-off-by: Alan Clucas <[email protected]>
Fixes #11610
Motivation
Workflows with parameterized global artifact names (e.g.,
globalName: output-result-{{inputs.parameters.variable}}) fail validation in exit handlers after v3.4.6 witherrors like "failed to resolve {{workflow.outputs.artifacts.output-result-car}}". This worked correctly in v3.4.5 and earlier.
Modifications
anyWorkflowOutputArtifactMagicValuewhen parameterized global artifacts existVerification
Documentation
No documentation changes needed - this restores existing functionality that was inadvertently broken.