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

Add linter rule for usage of kVersionContextIgnored

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We can bypass using the VersionContext in the feature flag API by passing-in a dummy kVersionContextIgnored value. This will make the feature-flag check rely on the node's local FCV only. Since this can potentially lead to inconsistent behaviour, this approach should be used with a lot of care.

      The goal of this ticket is the add a rule to the linter to make sure that every usage of kVersionContextIgnored is accompanied by a comment explaining the reasoning behind that choice.

            Assignee:
            Unassigned Unassigned
            Reporter:
            robert.sander@mongodb.com Robert Sander
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: