[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: |
|
||||||||
| 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: |