[SERVER-67839] Unify addTenantMigrationRecipientAccessBlocker logic. Created: 07/Jul/22 Updated: 27/Oct/23 Resolved: 25/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Christopher Caplinger |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | shard-merge-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Currently both createAccessBlockerIfNeeded() and tenant_migration_access_blocker::addTenantMigrationRecipientAccessBlocker() does the same thing i.e, creates and add the recipient blocker to the access blocker registry. Unify this logic and make the logic to be in tenant_migration_access_blocker namespace |