Add gateway namespace to gateway resources#19347
Conversation
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
There was a problem hiding this comment.
Pull request overview
This PR adds a gateway namespace to all MLflow AI Gateway resources to prevent future namespace conflicts. The changes systematically rename methods, RPC endpoints, and API paths to include "gateway" in their names.
Key changes:
- Renamed all gateway-related methods to include
gatewayprefix (e.g.,create_secret→create_gateway_secret) - Updated all API endpoint paths to include
/gateway/namespace (e.g.,/mlflow/secrets/create→/mlflow/gateway/secrets/create) - Updated RPC method names and documentation titles to reflect the gateway namespace
Reviewed changes
Copilot reviewed 9 out of 10 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| tests/tracking/test_rest_tracking.py | Updated integration test function calls to use new create_gateway_*, update_gateway_*, delete_gateway_*, get_gateway_*, and list_gateway_* method names |
| tests/store/tracking/test_rest_store.py | Updated unit test function names and method calls to use gateway-prefixed naming; updated expected API endpoint paths to include /gateway/ namespace |
| tests/store/tracking/test_gateway_sql_store.py | Renamed all test functions and updated method calls to use gateway-prefixed naming convention |
| mlflow/store/tracking/gateway/sqlalchemy_mixin.py | Renamed all public methods in the SQL store implementation to include gateway prefix |
| mlflow/store/tracking/gateway/rest_mixin.py | Renamed all public methods in the REST store mixin to include gateway prefix |
| mlflow/store/tracking/gateway/abstract_mixin.py | Updated abstract method signatures to include gateway prefix for consistency |
| mlflow/server/handlers.py | Updated handler functions to call the newly renamed gateway-prefixed store methods |
| mlflow/protos/service.proto | Updated RPC method names to include Gateway suffix, changed API paths to include /gateway/ namespace, updated RPC doc titles, and removed unused getSecretsConfig RPC |
| mlflow/java/client/src/main/java/org/mlflow/api/proto/Service.java | Auto-generated Java code reflecting the protobuf changes with updated method names and endpoint paths |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
|
Documentation preview for afdbe2d is available at: More info
|
BenWilson2
left a comment
There was a problem hiding this comment.
renames look great! If you merge tonight, I'll do the sync to get the UI updated to these routes :D Thanks @TomeHirata !!
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
| // ========== Secrets Configuration API ========== | ||
|
|
||
| // Get secrets storage configuration status | ||
| rpc getSecretsConfig(GetSecretsConfig) returns (GetSecretsConfig.Response) { |
There was a problem hiding this comment.
@BenWilson2 sorry, this rpc was removed since there's no usage for this rpc... Can you add it back in this PR?
🛠 DevTools 🛠
Install mlflow from this PR
For Databricks, use the following command:
Related Issues/PRs
n/a
What changes are proposed in this pull request?
Add gateway namespace to gateway resources to avoid future namespace conflicts.
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.