oxidecomputer / oxidecomputer/omicron
fm: implement Active Problems public API models and endpoints
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Part of #11029. Once we agree on the design of the Active Problems external API (see RFD 699, we'll need to implement the actual API types and endpoints for Active Problems.
This issue is just for adding the routes and model types to the API, not making them actually do anything (which will be tracked separately). For this to be considered completed, it will be fine for all the list APIs to return empty lists, and the GET-by-ID APIs to return 404s, since no Active Problems will actually exist.
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 by reading RFD 699 and the parent issue #11029 to understand the agreed Active Problems API design. Locate the existing API route and model structure, add the specified routes and types, and verify that list endpoints can return empty lists while GET-by-ID endpoints return 404s.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100