oxidecomputer / oxidecomputer/propolis
propolis-server HTTP API versioning + phd = ow
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
as experienced in #977: https://github.com/oxidecomputer/propolis/pull/977/files#r2582502490
I'm not even sure if we can nicely discover what the latest supported API for a propolis-server is, from just a git hash for base. but we'll want to pick a different client for the older API so we can drive the base propolis at all in these tests! (un)fortunately this has no relationship to the actual ability to migrate, which should work regardless.
Contributor guide
No contributing guide indexed for this repository
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
Begin with the files and review discussion linked from pull request #977, especially comment r2582502490. Determine how a base git hash can identify the latest supported propolis-server API and how tests should select a compatible client for older APIs. Done means tests can drive the base propolis while preserving migration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100