Support rollback for `config set`
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
Prior to set the current state via get is stored. If set fails, dsc can attempt a rollback to previous. It may make sense to have a --no-rollback switch for developers.
Proposed technical implementation details (optional)
If an application wants multiple levels of rollback, it's up to that application to store history.
If resources in the rollback state support _clobber, then those should be explicitly set to true.
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 tracing the config set and get command paths to understand how current state is read and how failures are reported. Define the rollback behavior, including the optional --no-rollback switch and _clobber handling, then identify or add tests covering successful sets, failed sets, and restoration of the prior state.
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
- 30/100