[SERVER-63599] Clean up donor data after tenant migration in TenantMigration python fixture Created: 11/Feb/22 Updated: 01/Mar/22 Resolved: 01/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Suganthi Mani |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Server Serverless 2022-03-07 | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
After a migration has completed and the fixture has sent donorForgetMigration, we should follow the production tenant migration steps to cleanup orphaned donor data. |
| Comments |
| Comment by Suganthi Mani [ 01/Mar/22 ] |
|
Closing this ticket as won’t fix for and we will reevaluate this work when we start working on shard merge testing work. |
| Comment by Steven Vannelli [ 22/Feb/22 ] |
|
matt.broadstone assigning this to you for BF Friday investigation. |