Rollback #56
Labels
No labels
attention
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-ruling
needs-triage
offsite
post-merge
ready
release
scope:bootstrap
scope:coolify
scope:db
scope:docs
scope:drill
scope:installer
scope:labels
scope:platform
scope:runner
scope:users
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/rig#56
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.