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

Solidify usage of the config singleton in Sherman

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11

      Right now we throw everything into the config singleton as a property of the object as nested namespaces. It makes it kind of hard to get config information like connection strings, ips, etc. and the usage is not well defined.

      The goal is to clean up the object usage in the codebase and come up with a new interface for the config object.

            adi.zaimi@mongodb.com Adi Zaimi
            jason.zhang@mongodb.com Jason Zhang
            0 Vote for this issue
            1 Start watching this issue