[SERVER-81787] Add support for ValidatedTenancyScope to ForwardableOperationMetadata Created: 03/Oct/23  Updated: 02/Jan/24  Resolved: 27/Nov/23

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

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

Issue Links:
Depends
is depended on by SERVER-81009 VTS not available on opCtx for Distin... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2023-11-13, Service Arch 2023-11-27
Participants:

 Description   

ForwardableOperationMetadata is our current solution for propagating operation metadata between operation contexts. The operation context (and really the ValidatedTenancyScope mounted on an opCtx) will soon become the source of truth for tenant domain, and so we need a way to propagate ValidatedTenancyScope between operation contexts. This ticket covers work to stash a ValidatedTenancyScope in ForwardableOperationMetadata so it can be applied to operation contexts constructed on behalf of a parent operation with tenant domain attached.



 Comments   
Comment by Githook User [ 27/Nov/23 ]

Author:

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

Message: SERVER-81787 Add support for ValidatedTenancyScope to ForwardableOperationMetadata
Branch: master
https://github.com/mongodb/mongo/commit/3e87549746ab3a4ac3c0a37ea66759e5f249fd1c

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