-
Notifications
You must be signed in to change notification settings - Fork 310
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
Adding missing fields to FlyteTask remote entity #3093
Adding missing fields to FlyteTask remote entity #3093
Conversation
Thank you for opening this pull request! 🙌 These tips will help get your PR across the finish line:
|
Code Review Agent Run #42cb06Actionable Suggestions - 1
Review Details
|
70784e4
to
ef01024
Compare
Changelist by BitoThis pull request implements the following key changes.
|
Code Review Agent Run #c16628Actionable Suggestions - 0Review Details
|
Code Review Agent Run #4cb82dActionable Suggestions - 0Additional Suggestions - 1
Review Details
|
Signed-off-by: Umer Ahmad <[email protected]> Signed-off-by: Umer Ahmad <[email protected]>
Signed-off-by: Umer Ahmad <[email protected]> Signed-off-by: Umer Ahmad <[email protected]>
d41336a
to
9a58c5a
Compare
Signed-off-by: Umer Ahmad <[email protected]>
Code Review Agent Run #17dd82Actionable Suggestions - 0Review Details
|
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.
the spark unit test failure is real. Can you take a look?
Signed-off-by: Umer Ahmad <[email protected]>
Head branch was pushed to by a user without write access
Code Review Agent Run #b0f738Actionable Suggestions - 0Additional Suggestions - 10
Review Details
|
Patched! - thanks for pointing it out, saw that plugins had a separate suite locally. And, it looks like the sagemaker test is globally failing. |
Correct. The sagemaker failures are not related to your PR. |
Congrats on merging your first pull request! 🎉 |
Tracking issue
flyteorg/flyte#6192
Why are the changes needed?
Missing fields from FlyteTask entity from remote, for example, we need k8s_pod for template data analysis, but it only includes container as of now.
What changes were proposed in this pull request?
Adding the following fields to FlyteTask init, and promotion from model (also config):
security_context
config
k8s_pod
sql
extended_resources
How was this patch tested?
unit tests
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
Enhanced FlyteTask remote entity with security_context, k8s_pod, sql, and extended_resources support, including default values and validation. Improved type system with strict type hint matching and added webhook task functionality with rate limiting for worker queues. Implemented shared memory support and enhanced caching capabilities across components. Added comprehensive test coverage and validation improvements for Ray tasks, remote execution, and type handling.Unit tests added: True
Estimated effort to review (1-5, lower is better): 5