[SERVER-85429] Make cluster parameter invocations create OpMsgRequest with ValidatedTenancyScope Created: 19/Jan/24 Updated: 05/Feb/24 |
|
| Status: | In Code Review |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | Sophia Tan |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ntdi_code_quality, ntdi_must_have | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Service Arch 2024-02-05, Service Arch 2024-02-19 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
|
In the call sites of `OpMsgRequestBuilder::create` in cluster parameter invocation , we need to use another factory function `createWithValidatedTenancyScope` to build OpMsgRequest with ValidatedTenancyScope. Also, in the related js tests, use security token instead of "$tenant"
|