oxidecomputer / oxidecomputer/omicron
Support Bundle API tweaks for range requests, error codes
Open
Nobody has claimed this yet.
api
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
- Support bundles would like to be able to propagate streaming bodies which also include error codes in the API spec. As an example of this, see: https://github.com/oxidecomputer/omicron/pull/7346 . This is currently limited by the fact that
FreeformBodydrops response headers, which would be necessary for range requests. - Support bundles would like to implement range requests in their API, by propagating requests from Nexus to Sled Agent. Unfortunately, although Nexus can parse these headers, they cannot be sent with the progenitor API as-is. This requires https://github.com/oxidecomputer/progenitor/pull/750 to be able to propagate request headers.
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 the issue requirements and the referenced omicron PR 7346 for streaming bodies with error codes. Then inspect progenitor PR 750, which is required for propagating request headers. Done means the Support Bundle API can preserve response headers for range requests, carry streaming error codes, and propagate range-request headers from Nexus to Sled Agent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100