stacklok / stacklok/toolhive-rfcs
Create an RFC for moving `thv` state into a proper database
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This was an outcome of a team retro. To summarize, the current system of storing run configs in files is brittle and has caused repeated pain. To better manage the version of this state, we want to put into a database, so we can use schema / migration tooling.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #40 and review how run configurations are currently stored in files. The RFC should explain the database-based state model and how schema and migration tooling would support versioning; the issue does not name specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100