Skip to content

RFC: Workload upgrade detection and application#68

Merged
JAORMX merged 2 commits into
mainfrom
jaosorior/rfc-workload-upgrade
Apr 30, 2026
Merged

RFC: Workload upgrade detection and application#68
JAORMX merged 2 commits into
mainfrom
jaosorior/rfc-workload-upgrade

Conversation

@JAORMX
Copy link
Copy Markdown
Contributor

@JAORMX JAORMX commented Apr 9, 2026

Summary

  • Add server-side upgrade detection for MCP server workloads, moving tag drift and env var drift logic from Studio's frontend into the ToolHive backend
  • New thv upgrade check and thv upgrade apply CLI commands
  • New GET /api/v1beta/workloads/upgrade-check API endpoints
  • Prerequisite: RegistryServerName field on RunConfig for reliable workload-to-registry mapping
  • 3-phase implementation plan respecting toolhive's PR size conventions

Test plan

  • Review RFC content for completeness and accuracy
  • Verify security considerations section addresses all required areas
  • Validate compatibility with existing workload lifecycle

🤖 Generated with Claude Code

JAORMX and others added 2 commits April 9, 2026 10:39
Propose server-side upgrade detection for MCP server workloads,
moving tag drift and env var drift logic from Studio's frontend
into the ToolHive backend. Adds thv upgrade CLI commands and
REST API endpoints so all clients benefit.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>
JAORMX added a commit to stacklok/toolhive that referenced this pull request Apr 9, 2026
Running workloads need to be mapped back to their registry entry by
name so that downstream consumers (e.g. the registry export endpoint)
can look up server metadata. Add a RegistryServerName field to
RunConfig following the same pattern as RegistryAPIURL and RegistryURL:
builder option, resolver helper, wiring through all three call sites,
and regenerated OpenAPI docs.

Part of stacklok/toolhive-rfcs#68

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ChrisJBurns pushed a commit to stacklok/toolhive that referenced this pull request Apr 9, 2026
Running workloads need to be mapped back to their registry entry by
name so that downstream consumers (e.g. the registry export endpoint)
can look up server metadata. Add a RegistryServerName field to
RunConfig following the same pattern as RegistryAPIURL and RegistryURL:
builder option, resolver helper, wiring through all three call sites,
and regenerated OpenAPI docs.

Part of stacklok/toolhive-rfcs#68

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@samuv samuv left a comment

Choose a reason for hiding this comment

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

Looks good! Happy to remove some logic in Studio

@JAORMX JAORMX merged commit 8c1292d into main Apr 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants