Documentation
¶
Overview ¶
Package exampleembedder demonstrates an embedder that obtains a live, Kubernetes-backed vMCP backend registry through the public backendregistry.NewKubernetesBackendRegistry constructor and wires it into the core+Serve assembly WITHOUT importing pkg/vmcp/k8s or k8s.io/client-go/rest.
It backs the acceptance tests for issue #5541: the import-graph test (backendregistry/importgraph_test.go) parses this package and asserts it imports neither the watch substrate nor the Kubernetes REST package, and the package compiling at all proves the constructor's return types plug directly into core.Config and server.ServerConfig.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func BuildServer ¶
BuildServer builds a live backend registry via the public constructor and wires it into core.New and server.Serve, returning the constructed *server.Server.
server.Serve only assembles the server; the caller must still call (*server.Server).Start to begin serving HTTP — hence "Build", not "Serve".
Types ¶
type Deps ¶
type Deps struct {
Aggregator aggregator.Aggregator
Router router.Router
BackendClient vmcp.BackendClient
SessionManagerConfig *sessionmanager.FactoryConfig
}
Deps are the core/transport collaborators the embedder wires itself. Only the BackendRegistry and the readiness Watcher come from the registry seam; the aggregator, router, backend client, and session manager remain the embedder's responsibility (out of scope for issue #5541).
Source Files