[ Gateway 9.5/10 ] Refactor the provider display for better UX#19503
Merged
BenWilson2 merged 1 commit intomlflow:masterfrom Dec 26, 2025
Merged
Conversation
This was referenced Dec 19, 2025
72777a4 to
b370741
Compare
This was referenced Dec 19, 2025
Contributor
There was a problem hiding this comment.
Pull request overview
This PR refactors the AI Gateway provider display to improve UX by:
- Creating compound provider listings that combine related providers (OpenAI/Azure OpenAI, Vertex AI variants)
- Separating LiteLLM-backed providers into a distinct section with navigation
- Adding comprehensive UI components for API key management, endpoints, and model configuration
- Enhancing the Python backend with additional authentication modes and model metadata fields
Reviewed changes
Copilot reviewed 112 out of 115 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| mlflow/utils/providers.py | Adds bedrock API key auth mode, sagemaker provider config, excludes bedrock_converse, adds model metadata fields |
| mlflow/server/js/src/lang/default/en.json | Adds 200+ internationalization strings for new UI features |
| mlflow/server/js/src/gateway/utils/*.ts | New utility modules for provider grouping, formatting, error handling, and date conversion |
| mlflow/server/js/src/gateway/hooks/*.ts | Comprehensive React Query hooks for data fetching and mutations |
| mlflow/server/js/src/gateway/components/*.tsx | New UI components for side navigation, secrets, API keys, and endpoints |
| mlflow/server/js/src/gateway/pages/*.tsx | Refactored main gateway page and new pages for API keys and endpoint management |
| mlflow/server/js/src/gateway/types.ts | Updated TypeScript type definitions with renamed interfaces and new fields |
The changes are well-structured with good separation of concerns, comprehensive test coverage for utility functions, and proper TypeScript typing throughout.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
|
Documentation preview for 8f42321 is available at: More info
|
b370741 to
8916ec0
Compare
This was referenced Dec 20, 2025
449716c to
6d2416a
Compare
ab3bf85 to
1200acc
Compare
b24ac74 to
ccb8f35
Compare
ccb8f35 to
8f42321
Compare
omarfarhoud
pushed a commit
to omarfarhoud/mlflow
that referenced
this pull request
Jan 20, 2026
…w#19503) Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
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.
🥞 Stacked PR
Use this link to review incremental changes.
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
Create a compound single-entity provider listing that combines Vertex provider listings, OpenAI / Azure OpenAI, and separates the LiteLLM-backed providers to a separate listing section (with navigation to move between the two main listings).
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.