feat: use fetch for Flyte API HTTP client#898
Merged
ursucarina merged 7 commits intomasterfrom Mar 31, 2026
Merged
Conversation
Signed-off-by: Carina Ursu <carina@union.ai>
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #898 +/- ##
=======================================
Coverage 54.61% 54.61%
=======================================
Files 585 585
Lines 15325 15390 +65
Branches 2804 2831 +27
=======================================
+ Hits 8369 8405 +36
- Misses 6956 6985 +29 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Carina Ursu <carina@union.ai>
Signed-off-by: Carina Ursu <carina@union.ai>
Signed-off-by: Carina Ursu <carina@union.ai>
Signed-off-by: Carina Ursu <carina@union.ai>
Signed-off-by: Carina Ursu <carina@union.ai>
wild-endeavor
approved these changes
Mar 31, 2026
Collaborator
|
🎉 This PR is included in version 1.21.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TL;DR
Malicious publishes were reported for affected axios versions on npm; see axios#10604 and Step Security’s write-up. Moving HTTP calls to native fetch removes reliance on axios for those code paths and shrinks the vulnerable surface
Type
Are all requirements met?
Complete description
Switches Flyte console API traffic from axios to the native fetch API
Changes
flyte-api:defaultFetchConfig/getFetchApiCall(and related helpers); request errors normalized viatransformRequestError.common:HttpRequestErrorand proto/response decoding tweaks as needed for the new path.oss-console: HTTP client wiring (axiosClient / data layer), hooks and models that performed GETs (useUserProfile, api.ts, admin paths), and error UI boundaries aligned with the new error shape.Tracking Issue
n/a