Repository navigation
Add manual production database refresh for development - #2
Merged
Merged
Conversation
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.
Add a manual database-only action to replace development D1 data with a current production snapshot. It preserves development settings and the whitelist, clears sessions and delivery state, applies pending development migrations offline, and requires the deployed development snapshot safeguards. It never merges code, deploys Workers or writes production data.
Validation: 317 main regression tests pass locally; fictional SQLite roundtrips cover migration compatibility, data integrity and atomic settings-change refusal; mocked orchestration verifies production export-only access, a single development import and private-file cleanup. Development guards passed 348 regression tests and Worker integration checks and are already deployed to the separate test Worker. Workflow syntax and complete reachable history passed privacy scans.
Activation: enable the independent database-refresh repository variable only in the canonical repository. The development-refresh environment still needs CLOUDFLARE_API_TOKEN. No real database refresh was run.