Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow HistoricDataDeletionWorker to delete Subscribers/SubscriberLists that have older inactive subscriptions. #1995

Closed
wants to merge 1 commit into from

Conversation

KludgeKML
Copy link
Contributor

  • add new scope for subscriptions that are either active or ended less than a week ago
  • add this scope to the selections in the worker so it can delete Subscribers or SubscriberLists if they only contain older ended subscriptions, so they more closely match what the original specs actually asked for.
  • replace .delete calls with .destroy calls in worker to allow rails to maintain db relation consistency (slower but correct, and worker does not need to be super performant)

https://trello.com/c/HFy9tpyE/2215-investigate-whether-historic-email-subscription-data-can-be-more-aggressively-deleted

⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

…s that have inactive subscriptions.

- add new scope for subscriptions that are either active or ended less than a week ago
- add this scope to the selections in the worker so it can delete Subscribers or SubscriberLists if they only contain older ended subscriptions, so they more closely match what the original specs actually asked for.
- replace .delete calls with .destroy calls in worker to allow rails to maintain db relation consistency (slower but correct, and worker does not need to be super performant)
@KludgeKML
Copy link
Contributor Author

Closing as I think this will be unnecessary if we simply clear the existing confusing bad lists.

@KludgeKML KludgeKML closed this Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant