Rollback #56

Closed
opened 2026-07-19 16:21:10 +00:00 by danmt · 1 comment
danmt commented 2026-07-19 16:21:10 +00:00 (Migrated from github.com)

it would be really cool to have a rollback mechanism in rig such that if a user makes a mistake or whatever, they get back to the pristine debian. if its too complex it can divided into multiple smaller issues

it would be really cool to have a rollback mechanism in rig such that if a user makes a mistake or whatever, they get back to the pristine debian. if its too complex it can divided into multiple smaller issues
dan-claude-bot commented 2026-07-19 17:35:58 +00:00 (Migrated from github.com)

Superseded by #62. Taking up the invitation to split — but the split falls out by kind of state rather than by role: snapshot-restore handles everything box-local (heavy-duty/box#104), while the tailnet join and the runner registration live off-box and survive any restore (#63). #62 is the parent with the reasoning and the checklist. Safe to close.

Superseded by #62. Taking up the invitation to split — but the split falls out by *kind of state* rather than by role: snapshot-restore handles everything box-local (heavy-duty/box#104), while the tailnet join and the runner registration live off-box and survive any restore (#63). #62 is the parent with the reasoning and the checklist. Safe to close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/rig#56
No description provided.