[AXS-52] Configuration manager redesign

djordjeglbvc commented 4 years ago

Summary Define new API for initializing config manager structure, reading config values and maybe registering new config options. Rethink possible config storage formats, currently it is stored in ini file, and options can also be set through command line arguments. Maybe possibility for support of different storage plugins.

Details

[x] Task 1: Define user API (initialization, reading, registering config options)
[x] Task 2: Define storage API (read from storage, maybe write modified values)

JIRA: AXS-52

djordjeglbvc commented 4 years ago

Decided to go with simple read-only user API consisting only of getters with input parameters for module name and option name. Decided against going with storage API, instead just defining callback functions for different config manager implementations. Only few simple callbacks need to be implemented - config init (initializes in memory config database), and getter functions for different data types. edit: I guess these callbacks can be considered as storage API

djordjeglbvc commented 4 years ago

Done, continued work on implementation is tracked in #62

iotaledger / access-server

[AXS-52] Configuration manager redesign #63