oxidecomputer / oxidecomputer/omicron
Do not allow deletion of the last remaining uplink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
It's likely that we do not have any guards in place to prevent customers from accidentally cutting themselves off from the rack, via deletion of their uplink config. We should implement some form of guard that prevents deletion of an uplink if it's the last one remaining.
Maybe bonus points if we can detect if there are more uplinks configured in the DB, but only one has an active LINK?
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 API entry point for deleting an uplink and the code that reads uplink configuration from the database. Trace how deletion is validated and determine how an active LINK is represented. Done means the last remaining uplink cannot be deleted, with coverage for the stated guard and any supported active-LINK case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100