Skip to content

[Workspace] Propagate workspace context through REST APIs#19282

Merged
BenWilson2 merged 1 commit intomlflow:orgnization-supportfrom
mprahl:workspace-handlers
Dec 10, 2025
Merged

[Workspace] Propagate workspace context through REST APIs#19282
BenWilson2 merged 1 commit intomlflow:orgnization-supportfrom
mprahl:workspace-handlers

Conversation

@mprahl
Copy link
Collaborator

@mprahl mprahl commented Dec 9, 2025 •
edited by github-actions bot
Loading

🛠 DevTools 🛠

Open in GitHub Codespaces

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19282/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19282/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/19282/merge

Related Issues/PRs

#1464
#5844
Design document: https://docs.google.com/document/d/1IbFfceCmWV3knJfc0ninn58EXLVbHUh1meV_pknOM40/edit

What changes are proposed in this pull request?

Add Flask and FastAPI middleware to resolve the active workspace and set the workspace context. This allows workspace aware stores to directly leverage this without resolving it themselves. Artifact serving is also isolated by workspace when enabled.

Also enhance the server CLI with workspace configuration options.

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/tracking: Tracking Service, tracking client APIs, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How 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" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should 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?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

@github-actions github-actions bot added the rn/none List under Small Changes in Changelogs. label Dec 9, 2025
@mprahl
Copy link
Collaborator Author

mprahl commented Dec 9, 2025

/cc @B-Step62 @BenWilson2

@B-Step62 B-Step62 force-pushed the orgnization-support branch from c1ca273 to 2705ccd Compare December 9, 2025 02:24
BenWilson2
BenWilson2 reviewed Dec 9, 2025
View reviewed changes
BenWilson2
BenWilson2 reviewed Dec 9, 2025
View reviewed changes
BenWilson2
BenWilson2 reviewed Dec 9, 2025
View reviewed changes
BenWilson2
BenWilson2 reviewed Dec 9, 2025
View reviewed changes
mlflow/utils/server_cli_utils.py
# Workspace mode relies on a workspace provider to resolve the default workspace and seed
# request context. Artifact-only servers never load that stack, so they cannot determine
# the active workspace safely. This decision can be revisited in the future.
raise click.UsageError("--enable-workspaces cannot be combined with --artifacts-only.")
Copy link
Member

@BenWilson2 BenWilson2 Dec 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this fine to leave for future work if requested. The very nature of this feature stack seems like running an artifacts-only server seems like it's not common for where users would run in this mode.

@mprahl mprahl force-pushed the workspace-handlers branch 4 times, most recently from 26d2b12 to ff12f59 Compare December 9, 2025 20:28
BenWilson2
BenWilson2 approved these changes Dec 9, 2025
View reviewed changes
Copy link
Member

@BenWilson2 BenWilson2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the work here, Matt! This looks great :)

@github-actions
Copy link
Contributor

github-actions bot commented Dec 9, 2025 •
edited
Loading

Documentation preview for 950ba8a is available at:

More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

@mprahl mprahl force-pushed the workspace-handlers branch 2 times, most recently from 84986a0 to 37c4f44 Compare December 9, 2025 21:27
@mprahl
Propagate workspace context through REST APIs
950ba8a 
Add Flask and FastAPI middleware to resolve the active workspace and set
the workspace context. This allows workspace aware stores to directly
leverage this without resolving it themselves. Artifact serving is also
isolated by workspace when enabled.

Also enhance the server CLI with workspace configuration options.

This also includes a few fixes after the rebase to the master branch.

Signed-off-by: mprahl <mprahl@users.noreply.github.com>
@mprahl mprahl force-pushed the workspace-handlers branch from 37c4f44 to 950ba8a Compare December 9, 2025 22:11
@BenWilson2 BenWilson2 merged commit 17dbc58 into mlflow:orgnization-support Dec 10, 2025
47 checks passed
@mprahl mprahl deleted the workspace-handlers branch December 10, 2025 02:24
mprahl added a commit to mprahl/mlflow that referenced this pull request Jan 16, 2026
@mprahl
[Workspace] Propagate workspace context through REST APIs (mlflow#19282)
24e6ee8 
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
B-Step62 pushed a commit to B-Step62/mlflow that referenced this pull request Jan 19, 2026
@mprahl @B-Step62
[Workspace] Propagate workspace context through REST APIs (mlflow#19282)
3add51b 
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
B-Step62 pushed a commit to B-Step62/mlflow that referenced this pull request Feb 3, 2026
@mprahl @B-Step62
[Workspace] Propagate workspace context through REST APIs (mlflow#19282)
2586c77 
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
mprahl added a commit to mprahl/mlflow that referenced this pull request Feb 3, 2026
@mprahl
[Workspace] Propagate workspace context through REST APIs (mlflow#19282)
872fbdd 
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@BenWilson2 BenWilson2 BenWilson2 approved these changes

Assignees

@BenWilson2 BenWilson2

Labels

rn/none List under Small Changes in Changelogs.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mprahl @BenWilson2