[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:
Duplicate
duplicates SERVER-72081 Change the access blocker registry da... Closed
Related
is related to SERVER-71186 Tenant migration access blocker regis... Closed
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.


Generated at Thu Feb 08 06:19:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.