Skip to content

refactor(api): move MCP header resolution out of v1alpha3 (v1.0.x backport) - #3600

Closed
EItanya wants to merge 1 commit into
backport/v1.0.x/04-3562from
backport/v1.0.x/05-3563
Closed

EItanya wants to merge 1 commit into
backport/v1.0.x/04-3562from
backport/v1.0.x/05-3563

Conversation

@EItanya

@EItanya EItanya commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

# Description

`go/api/v1alpha3` is the public API that external clients and wrapper
types import, but it pulled in controller-runtime and `database/sql` for
a few helpers that do I/O. This moves those helpers out so the API
package only describes data.

`RemoteMCPServerSpec` loses its `sql.Scanner`/`driver.Valuer` methods,
which nothing used. `RemoteMCPServer.ResolveHeaders`,
`ValueRef.Resolve`, and `ValueSource.Resolve` move into the tool
service's MCP client, their only caller, and `go/api/utils` is removed.
The translator keeps its existing `HeadersFrom` handling, which compiles
Secret-backed headers into egress credentials rather than reading them.

Header resolution behaves the same, except errors are now wrapped and
name the failing header. Go consumers that called the removed methods
need to read the referenced Secret or ConfigMap themselves.

Signed-off-by: timflannagan <timflannagan@gmail.com>
(cherry picked from commit c6adf72)
Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>
@EItanya

EItanya commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

Closing: the team decided to leave release/v1.0.x as it is for stability, so neither the revert of #3586 nor the re-stacked backports will land.

Comment left by Claude on behalf of @EItanya

@EItanya EItanya closed this Nov 9, 2026
@EItanya
EItanya deleted the backport/v1.0.x/05-3563 branch November 10, 2026 13:55
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