[SERVER-81530] Solidify usage of the config singleton in Sherman Created: 28/Sep/23  Updated: 07/Dec/23  Resolved: 07/Dec/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jason Zhang Assignee: Adi Zaimi
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: 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
Participants:

 Description   

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.


Generated at Thu Feb 08 06:46:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.