Skip to content

[Kubernetes MCPRegistry] Split thv-registry-api #2103

@dmartinol

Description

@dmartinol

Overview

To make the thv-registry-api project usable by others without having to use the rest of ToolHive, we would like to move the thv-registry-api binary to a separate repository.

Deliverables

  • A new repository is created with the code that builds thv-registry-api
  • The repository has no dependencies outside public packages
  • The repository builds a container image through a GitHub action
  • The repository maintainers are the same as Toolhive maintainers for the start
  • The README.md will be the only documentation we have, we don't document thv-registry-api in the toolhive docs for start
  • Actions like build, lint, test are present in the repo
  • A CI job that make sure we adhere to the upstream openapi API spec
  • Renovate is configured

Non-goals

  • No separate documentation except for README

Migration process

  • We will not accept patches to the toolhive repository that modify thv-registry-api until the migration is done
  • When the migration is done, we will change the reference to the built image in the MCPRegistry controller to point to the new image.

Metadata

Metadata

Assignees

Labels

apiItems related to the APIenhancementNew feature or requestkubernetesItems related to Kubernetesregistry

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions