[SERVER-62341] Use failpoint to check whether tenantId is required in TenantNamespace Created: 04/Jan/22 Updated: 04/Jan/22 Resolved: 04/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Server Serverless 2022-01-10 |
| Participants: |
| Description |
|
A few existing security tests use the supportMultitenancy parameter already, and when run on the all feature flags variants will crash when constructing a TenantNamespace because featureFlagRequireTenantId is enabled, but not all callers will have the tenantId available to them yet. Change the check in the TenantNamespace constructor to check whether a failpoint is enabled rather than the feature flag for now. Once the work to always set the tenantId on the opCtx and to add tenantId to oplog entries is done, we can switch back to using the feature flag. |
| Comments |
| Comment by Janna Golden [ 04/Jan/22 ] |
|
Disabling featureFlagRequireTenantId instead. |