Current DirMgrConfig makes every new config section a breaking change
Due to the current structure of DirMgrConfig
, any time I want to add a new configuration section to DirMgrConfig
, this causes a breaking change. That seems undesirable: usually, adding new features should be possible without a breaking API change. We have managed to avoid this property with our config system as a whole.
As I recall, the rationale for structuring DirMgrConfig
in this way was to make absolutely certain that we couldn't introduce a new configuration section in DirMgrConfig
while forgetting to add it to TorConfig
. Any new solution should try to retain that property.
cc @Diziet