oxidecomputer / oxidecomputer/omicron
must not be able to delete the Recovery Silo
Open
Nobody has claimed this yet.
Good for new hires
important non-blocker
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I'm not sure yet how to enforce this without either a bit in the "silo" table or requiring this Silo to have a well-known name (which is not currently the case).
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
The issue does not name files, tests, or an entry point. First determine how Recovery Silo deletion is represented and handled, then decide how its protected status should be identified and verify that deletion is rejected without affecting other Silos.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100