Remove fcv_context_unaware parameter once all feature flags are converted to the new API

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.2.0-rc0
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • 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.

      SERVER-101559 then added a fcv_context_unaware IDL parameter which tracks which feature flags are still using the old API.

      Once all feature flags are converted (i.e. no feature flags with fcv_context_unaware: true remain), the fcv_context_unaware IDL parameter should be removed to avoid simplify the implementation and avoid confusion.

            Assignee:
            Unassigned
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: