oxidecomputer / oxidecomputer/omicron
Need system-level endpoints for TLS certs (current ones are silo-scoped)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Customer reports that the fleet admin is unable to update the TLS certificates of silos in which he isn't an admin. It is an awkward experience because he owns the wildcard cert and can use it for new silos. It's a reasonable expectation for the fleet admin to have CRUD endpoint like /system/silos/{silo}/certificate.
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 locating the existing silo-scoped TLS certificate endpoints and their API tests, then compare their authorization and CRUD behavior with the requested /system/silos/{silo}/certificate entry point. Done means fleet administrators can manage certificates for silos they do not administer, with coverage for the supported CRUD operations and authorization cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100