Refactor MultitenancyCheck

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Service Arch 2024-01-08, Service Arch 2024-01-22, Service Arch 2024-02-05, Service Arch 2024-02-19
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      MultitenancyCheck was added as a workaround to skip $tenant checks in the mongo bridge process. This is because the `op_msg.cpp` is shared between various process (such as mongod, mongos, mongo bridge, etc) and contains a tenant-related check relying on `multitenancySupport`.

      Now that $tenant is being removed `MultitenancyCheck` doesn't really makes sense because we don't use the class to perform checks. Instead we perform an `uassert` on the token if `MultitenancyCheck` exists otherwise we skip the uassert. This produces "correct" logic because the object exists in mongod and mongos but not mongo bridge. However the implementation is not very elegant or clean.

              Assignee:
              Dominic Hernandez (Inactive)
              Reporter:
              Didier Nadeau
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: