oxidecomputer / oxidecomputer/oxide.rs
ACK when deleting a bundle
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 75
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Target component
- CLI
- SDK
- Something else
- Not sure
Overview
Looks like it does take a bit for a bundle to get deleted, and while the bundle does get removed, it might be nice to let the user know that their request is indeed getting processed.
If one checks the list of bundles a second or 2 after the request goes through, the -allegedly- deleted bundle in still show up. Sending an ACK back would cope with the uncertainty.
Implementation details
Other processes, like instance creation, deliver this already. Something similar?
Anything else you would like to add?
No response
Contributor guide
No contributing guide indexed for this repository
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 tracing the CLI's bundle-delete command and compare its response handling with instance creation, which the issue says already provides an acknowledgement. Done means a bundle deletion request gives the user immediate confirmation that processing has started, without changing the deletion behavior; verify the response and the follow-up bundle listing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 57/100