Enable best effort error handling strategy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
During a config set (and really most config subcommands), if a resource instance fails, I would like for any independent resources to continue to be set. This best effort strategy allows for long running configurations to make progress toward their goal despite not being able to complete it.
Related, this would necessitate result output to be generated, including the results for successful, failed, and skipped resource instances.
This could also be an option added to the config command if it is deemed not appropriate as the default behavior.
Proposed technical implementation details (optional)
No response
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 Rust implementation of the config command, especially config set, and read how resource failures currently affect independent resources. Trace the existing result output path and define how successful, failed, and skipped instances should be reported before deciding whether best-effort behavior is an option or the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100