Revisit propagation of VersionContext to FeatureFlagAllMongodsAreSharded checks

XMLWordPrintableJSON

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

      Since FeatureFlagAllMongodsAreSharded is fully disabled [1, 2], it's use in the codebase has not been fully adapted to rely on the proper VersionContext during checks. This was done to avoid polluting the codebase by propagating the VersionContext across multiple layers, just to check a feature flag that is disabled and might be a candidate for deprecation (note that the All Clusters Sharded Intiative has been discontinued).

      The use of FeatureFlagAllMongodsAreSharded should be revisited in case we decide to enable it at some point. 

              Assignee:
              Unassigned
              Reporter:
              Robert Sander
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: