-
Notifications
You must be signed in to change notification settings - Fork 670
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
Add executionClusterLabel #5394
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5394 +/- ##
=======================================
Coverage 61.10% 61.11%
=======================================
Files 793 793
Lines 51164 51169 +5
=======================================
+ Hits 31265 31270 +5
Misses 17027 17027
Partials 2872 2872
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Rafael Raposo <[email protected]>
Signed-off-by: Eduardo Apolinario <[email protected]>
Signed-off-by: Eduardo Apolinario <[email protected]>
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.
Thank you!
docs failures are unrelated, the fix for that being #5425. |
* wAdd executionClusterLabel Signed-off-by: Rafael Raposo <[email protected]> * Run make -c flytectl generate Signed-off-by: Eduardo Apolinario <[email protected]> --------- Signed-off-by: Rafael Raposo <[email protected]> Signed-off-by: Eduardo Apolinario <[email protected]> Co-authored-by: Eduardo Apolinario <[email protected]>
Tracking issue
Closes #5395
Why are the changes needed?
To add
flytectl
the ability to select what execution it should go to.What changes were proposed in this pull request?
Add a new field in the execution spec.
How was this patch tested?
With a unit test