oxidecomputer / oxidecomputer/opte
Need API version for Oxide VPC API
Open
Nobody has claimed this yet.
mvp
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
While writing up #227 I realized that we also need a version number of the Oxide VPC API.
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 issue #227 to understand the Oxide VPC API context and why a version number is needed. Identify where the API version should be defined or documented; the issue is done when the versioning approach and its implementation scope are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100