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.
Why are the changes needed?
This PR upstreams most of a change from union (see "Add fields to NodeExecutionEvent").
What changes were proposed in this pull request?
From upstream,
The solution proposed here is to simply have propeller add the subworkflow ID, since propeller has this information already readily accessible in the node execution context.
Propeller also adds a boolean to the NodeExecutionEvent indicating whether or not this node corresponds to an entity that was at some point, generated by a dynamic task. Once a dynamic task runs, it comes with its own set of task and subworkflow definitions. This boolean just indicates to the events handler to not try to look up task/workflow template information in the Admin db as they may not even have been registered.
Changes
*Add IsInDynamicChain to the ImmutableParentInfo interface.
However, the part that actually adds the subworkflow id is not available, as it relies on another change that will not be upstreamed (ExecutableSubWorkflow interface doesn’t have GetIdentifier)
How was this patch tested?
Tested in union.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link