Clarify disaster-recovery doc's automation status - #1302
Open
victorisiguzoruzoma874 wants to merge 1 commit into
Open
Clarify disaster-recovery doc's automation status#1302victorisiguzoruzoma874 wants to merge 1 commit into
victorisiguzoruzoma874 wants to merge 1 commit into
Conversation
) backup_state.sh and restore_state.sh have no automated test coverage today, and backup.yml only fires on schedule/manual-dispatch. Make the doc explicit that the backup/restore drill, network confirmation prompts, mainnet type-to-confirm guard, and in-flight match recreation are all currently manual, so operators don't assume CI verifies any of it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
: confirms
docs/disaster-recovery.mdcorrectly reflects that the backup/restore cycle has zero automated CI coverage today.backup_state.sh/restore_state.share invoked by no test in the repo,backup.ymlonly runs on schedule/manual dispatch, and the network confirmation prompt, mainnet type-to-confirm guard, and in-flight match recreation are all manual operator steps.Scope note
Per current instruction, the integration-test and adversarial-test tasks in #1285 (local-network backup/restore harness, schema-version-mismatch rejection test, etc.) are out of scope for this PR — only the documentation-accuracy task was completed.
Test plan
bash scripts/check_doc_conformance.shpasses locally (no drift detected)