-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Service Arch
-
Service Arch 2024-02-19, Service Arch 2024-03-04, Service Arch 2024-03-18, Service Arch 2024-04-01, Service Arch 2024-04-15, Service Arch 2024-04-29
-
4
In order to ensure that the tenancy scope is always considered when parsing database strings (NamespaceString, DatabaseName), we should improve the IDlParserContext to require a ValidatedTenancyScope parameter. This means we must always have access to an opCtx, or have stashed a ValidatedTenancyScope somewhere convenient, before attempting to parse BSON into an IDL shape. There are valid use cases for not using a ValidatedTenancyScope when parsing, but by making the parameter required we force users to explicitly mark the cases where we don't care about tenant domain while parsing (a good example is in unit tests).
- depends on
-
SERVER-87788 Make IDLParserContext constructors take in a required ValidatedTenancyScope
- Closed
-
SERVER-87813 Make IDLParserContext constructor take in a ValidatedTenancyScope
- Closed
- has to be done after
-
SERVER-82352 Replace tenantId and SerializationContext with ValidatedTenancyScope in IDLParserContext constructor
- Closed