Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-101559

Force new feature flag checks to use operation FCV-aware checks

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: 8.1.0-rc0
    • Component/s: Upgrade/Downgrade
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-03-17, CAR Team 2025-03-31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-99351 introduced a new API for the FCV-gated feature flags that checks them against the operation FCV, if one is available. However, to ease the transition into the new API, it also introduced a transitional LegacyContextUnawareFCVGatedFeatureFlag type which keeps the old API, doesn't take the operation FCV into account.

      To ensure that going forward all feature flags use the new API, this ticket will add a file listing all existing FCV-gated feature flags. The feature flags in that list will be generated with the LegacyContextUnawareFCVGatedFeatureFlag transitional type, but new feature flags will be generated with the FCVGatedFeatureFlag type, and thus be forced to use operation FCV-aware checks.

      An additional benefit of having this list is that it will allow us to keep track of the feature flag conversion progress as well as keep feature flags such as featureFlagReplicaSetEndpoint using the old API until a decision is made about them.

            Assignee:
            joan.bruguera-mico@mongodb.com Joan Bruguera Micó
            Reporter:
            joan.bruguera-mico@mongodb.com Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None