TritonDataCenter / TritonDataCenter/node-triton
would like -f / --force for idempotent deletion
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 36
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
For at least volumes and instances, it would be nice if:
triton volume rm -f <volume>
and
triton rm -f <instance>
worked like:
rm -f
where the object already not existing is not treated as an error. This would make things nicer for scripts that automate creation/destruction of instances or volumes, since they could attempt to remove previous objects before creating new ones, and would not have to deal with parsing which type of failure they had doing deletion.
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 locating the command handlers for triton volume rm and triton rm, then trace how missing volumes and instances are reported during deletion. Implement the requested -f/--force behavior for both commands and verify that absent objects no longer cause an error while other deletion failures still do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100