[SERVER-71673] Refactor TenantMigrationAccessBlockerRegistry internal data structure to use TenantId Created: 29/Nov/22 Updated: 01/Mar/23 Resolved: 01/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Serverless
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The current internal data structure still uses StringData. This should change in favor of TenantId. The current model of this class has methods that uses either TenantId or StringData to add / remove tenantIds. This ticket covers the work to no longer use both and only use TenantId. Every method that is defined twice to handled both StringData and TenantId should be reduce to only keeping one method that uses the TenantId object type. |