Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-71673

Refactor TenantMigrationAccessBlockerRegistry internal data structure to use TenantId

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Serverless

      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.

            Assignee:
            backlog-server-serverless [DO NOT USE] Backlog - Server Serverless (Inactive)
            Reporter:
            mathis.bessa@mongodb.com Mathis Bessa (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: