[SERVER-81548] OpMsgRequest checks for expectPrefix in ValidatedTenancyScope OR command body Created: 28/Sep/23  Updated: 31/Oct/23  Resolved: 31/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Mathis Bessa
Resolution: Fixed Votes: 0
Labels: ntdi_must_have
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-81544 Track protocol=atlasproxy on client c... Closed
Duplicate
is duplicated by SERVER-81804 Remove support for reading expectPref... Closed
Gantt Dependency
has to be done before SERVER-82319 simulate_atlas_proxy override only co... Closed
Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2023-10-30, Service Arch 2023-11-13
Participants:

 Description   

We currently support expectPrefix optionally in the command body for all commands. After we complete SERVER-81544, we should check the ValidatedTenancyScope as the primary source of truth for the tenant protocol. We can't remove the check of the command body yet since our testing infrastructure still depends on that feature, we'll remove support for that in the next few tickets.



 Comments   
Comment by Githook User [ 31/Oct/23 ]

Author:

{'name': 'Mathis Bessa', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}

Message: SERVER-81548 OpMsgRequest checks for expectPrefix in ValidatedTenancyScope OR command body
Branch: master
https://github.com/mongodb/mongo/commit/44892d32f55428d79cfd4dbb4b9dc06daf6e9554

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