Record checkpoint throughout the workflow instead of only on error
Open
area/cli
kind/enhancement
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
We want the checkpoint file to be populated as tasks succeed instead of only at the end when an error occurs.
**Why is this needed**:
This would allow the user to use the checkpoint file to resume their cluster operations even if they terminate the process by using something like `Ctrl+C`
Contributor guide
Research direction
The issue does not name a file, test, or entry point. Locate the checkpoint handling and workflow task-completion paths, then trace how interruption and resume currently work; done means the checkpoint reflects successful tasks before an error or Ctrl+C and supports resuming cluster operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100