feat: enable onExit handlers to access DAG task outputs via workflow.outputs.parameters Fixes #14767 #14842
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
onExit handlers can now reference DAG task outputs using {{workflow.outputs.parameters.*}}
Fixes #14767
Motivation
In Argo Workflows, the onExit handler cannot access DAG task outputs through
workflow.outputs.parameters.*. Due to this limitation, users are unable to implement cleanup or notification logic that depends on the results of DAG task executions.Modifications
1. Runtime Logic
2. Validation Logic
workflow.outputs.parameters.*pattern is valid across different validation pathsVerification
validation and runtime execution both pass successfully
1. Submission-time Validation Test
Expected Result: YAML output (validation passes)
Failure Case: failed to resolve {{workflow.outputs.parameters.foo-replicas}} error
2. Runtime Execution Test
Expected Result: Exit handler can access: task output
Failure Case: Exit handler can access: (empty value)
Documentation
Example yaml