feat: configure hosted file retention per account - #9
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.
Hosted files currently expire after seven days for every account. Add an operator-controlled per-account retention setting: default seven days, 1–3,650 days, or zero for no automatic expiry. Storage, transfer and sharing limits remain unchanged.
New longer-lived uploads use a persisted
retained/R2 prefix so the existingusers/eight-day lifecycle cannot delete them. Permanent files returnexpiresAt: null; cleanup still reclaims pending/deleting files, and shared links still expire within 24 hours. The gallery shows the account's actual retention and each file's expiry.Migration 0005 is additive and preserves existing files and their expiry. The guide documents the setting, lifecycle checks and the prohibition on rolling back to cleanup code that does not understand permanent files or the new prefix.
Validation: 22 file tests against real local D1/R2, UI tests, typecheck and a real browser scenario covering 90-day, permanent and default seven-day accounts. Independent review before push. Production lifecycle inspected: object deletion applies only to
users/; owner account has no existing files.