Closed va6996 closed 1 week ago
Thank you for opening this pull request! 🙌
These tips will help get your PR across the finish line:
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 61.08%. Comparing base (
25c3596
) to head (33eb707
). Report is 1 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Congrats on merging your first pull request! 🎉
Tracking issue
Today if a user creates an execution with the
execution-cluster-label
, then the execution launches in the specified cluster. However, if the workflow has a reference workflow in the workflow, that reference workflow launches in the default cluster since this information isn't passed along. This change fixes that issue by inheriting the cluster label from the source.Why are the changes needed?
Without this change, part of the workflow will run in cluster 1 and part in cluster 2.
How was this patch tested?
In a local cluster, a workflow was launched with a reference workflow and the reference workflow launched in the correct cluster.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link