Add expiration, deletion, and storage reclamation for provisioned sites#2111
Merged
Conversation
# Conflicts: # packages/runtime-cloudflare/src/d1-operation-repository.ts # packages/runtime-cloudflare/src/provisioning-api.ts # packages/runtime-cloudflare/src/worker.ts # tests/cloudflare-provisioning-api.test.ts
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
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
Adds a generation-bound lifecycle for elastic Cloudflare WordPress allocations with owner controls, grace retention, teardown fencing, bounded reclamation, immutable receipts, and terminal quota release.
What changed
How to test
npm run build; expect TypeScript project build succeeds.npm run test:cloudflare-runtime; expect Cloudflare runtime, lifecycle race, reclamation, and provisioning suites pass.npm run cloudflare:dry-run:d1; expect Wrangler validates the D1 Worker bundle without deployment.Compatibility
Configured static sites without lifecycle rows retain existing behavior. Existing provisioning authorization, idempotency, and response contracts remain compatible. Anonymous immutable publication reads remain R2-only during grace.
Evidence
AI assistance
Source relationships