-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Repl 2023-11-13, Repl 2023-11-27, Repl 2023-12-11, Repl 2023-12-25
In https://jira.mongodb.org/browse/SERVER-70202 we changed isEnabled to invariant when FCV is uninitialized. However, we may not actually want to do this in all cases, since this would potentially turn a feature off when the FCV would be set to latest once initial sync is finished, so the user would actually expect it to be on.
This should potentially be done as part of/after SERVER-82064 to create passthrough suites for this situation so we can properly audit our feature flag use cases and make sure they don't invariant
- depends on
-
SERVER-79317 Provide more documentation and helper functions for case where feature flag checks could be run when fCV is uninitialized during initial sync
- Closed
-
SERVER-82064 Create passthrough suite that pauses initial sync while FCV is uninitialized
- Closed
- is depended on by
-
SERVER-84275 Change tenant ID feature flag to use isEnabled
- Closed
- related to
-
SERVER-80901 Audit gFeatureFlagServerlessChangeStreams
- Closed