oxidecomputer / oxidecomputer/omicron

Recursive project delete

Open
#4,674 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

By design, delete operations on any resource fail when the resource has children. In order to delete a whole project containing instances, disks, VPCs, etc., one currently has to build the tree of resource and delete everything from the leaves up. The problem is: that is often something we want to do! Currently we have some scripts that do this client-side. That may be where we land (maybe, for example, incorporating this logic into the CLI) but I wanted to track the possibility of doing this within the API. It would be a pretty complex and slow operation involved stopping potentially many instances and deleting many resources. It would probably make sense to wait for #392.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the context in issue #392 and the existing client-side scripts that delete project resources from the leaves up. Determine whether the desired outcome belongs in the API or CLI, and define completion around safely stopping and recursively deleting all project resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
cli
Domain
api, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.