oxidecomputer / oxidecomputer/omicron
want API endpoint for updating Silo
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Particularly after #3349, it'll be important to be able to modify Silos.
When we do this, we'll want to be careful about the privilege check we use. The Silo config can confer Fleet-level privileges and we should probably check whether you can ModifyPolicy on the Fleet to change that field.
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 #3349 and tracing the existing Silo API entry points; this issue names no file or test to begin with. Determine which Silo configuration can be updated and how the ModifyPolicy check on the Fleet should govern privilege-bearing changes. Done means the update behavior and its privilege boundary are clearly defined and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100