[SERVER-81825] Only support building OpMsgRequest with ValidatedTenancyScope Created: 03/Oct/23  Updated: 05/Feb/24

Status: In Progress
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Sophia Tan
Resolution: Unresolved Votes: 0
Labels: ntdi_code_quality
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-82680 Make FLE encrypted client use unsigne... In Code Review
is depended on by SERVER-84719 Remove dollar tenant in OpMsgRequest Needs Scheduling
Gantt Dependency
has to be done before SERVER-86029 Stop parsing and setting expectPrefix... Needs Scheduling
Issue split
split to SERVER-85429 Make cluster parameter invocations cr... In Code Review
split to SERVER-85479 Make UMCTransaction to build OpMsgReq... In Code Review
split to SERVER-85994 Make sharding code build request with... In Code Review
split to SERVER-85992 Ensure OpMsgRequest::fromDBAndBody ca... In Progress
split to SERVER-85253 Support extra fields and remove Seria... Closed
split to SERVER-85993 Make DbClient build request with Vali... Needs Scheduling
Assigned Teams:
Service Arch
Sprint: Service Arch 2024-01-22, Service Arch 2024-02-05, Service Arch 2024-02-19
Participants:
Story Points: 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.


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