Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Service Arch
-
Service Arch 2024-01-22, Service Arch 2024-02-05, Service Arch 2024-02-19
-
4
Description
The OpMsgRequestBuilder currently supports creating requests with and without a ValidatedTenancyScope. Requiring a ValidatedTenancyScope will help ensure that we either are always correctly propagating the tenant domain information, or very explicitly deciding not to include it.
Attachments
Issue Links
- depends on
-
SERVER-82680 Make FLE encrypted client use unsigned security token
-
- In Code Review
-
- has to be done before
-
SERVER-86029 Stop parsing and setting expectPrefix in command body in OpMsgRequest code
-
- Needs Scheduling
-
- is depended on by
-
SERVER-84719 Remove dollar tenant in OpMsgRequest
-
- Needs Scheduling
-
- split to
-
SERVER-85429 Make cluster parameter invocations create OpMsgRequest with ValidatedTenancyScope
-
- In Code Review
-
-
SERVER-85479 Make UMCTransaction to build OpMsgRequest with ValidatedTenancyScope
-
- In Code Review
-
-
SERVER-85994 Make sharding code build request with ValidatedTenancyScope
-
- In Code Review
-
-
SERVER-85992 Ensure OpMsgRequest::fromDBAndBody call sites build requests with ValidatedTenancyScope
-
- In Progress
-
-
SERVER-85253 Support extra fields and remove SerializationContext in building OpMsgRequest with ValidatedTenancyScope
-
- Closed
-
-
SERVER-85993 Make DbClient build request with ValidatedTenancyScope
-
- Needs Scheduling
-