Add organization-level retention enforcement#209
Open
quickweb-stack wants to merge 2 commits intoCredenceOrg:mainfrom
Open
Add organization-level retention enforcement#209quickweb-stack wants to merge 2 commits intoCredenceOrg:mainfrom
quickweb-stack wants to merge 2 commits intoCredenceOrg:mainfrom
Conversation
|
@quickweb-stack Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Author
|
Done, Close: #209 |
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
2 participants
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.
Close: #136
Implemented organization-level retention enforcement and committed it as 1399498 (Add organization-level retention enforcement).
The change adds a durable org-scoped retention model and audit trail in [004_add_organization_retention.ts], plus repositories for organizations, policy resolution, and batched cleanup in [organizationRepository.ts], [retentionPolicyRepository.ts], and [retentionRecordRepository.ts]. Cleanup runs through the new worker in [retentionCleanupWorker.ts], using bounded batches and global-policy fallback with org overrides; it’s wired into startup in [index.ts].
Focused tests passed:
npm test -- retentionPolicyRepository retentionCleanupWorker
I also verified the requested policy-resolution order and cleanup eligibility with new tests in [retentionPolicyRepository.test.ts] and [retentionCleanupWorker.test.ts].
The full npm run build still fails in this repo for pre-existing unrelated TypeScript issues outside this feature area, so I did not treat that as a blocker for this retention change.