The entire configuration is on a file-system. But it could be useful to have it inside an object storage.
Functionnalities
Have the choice between a file and an object storage. The choice is made for the entire configuration.
Be able to read the configuration inside an object storage
Tasks
Before coding
[ ] Choose an object storage
[ ] Specify the new IO of the CLI (ROAD2_CONF_FILE will still exist but there will be new ones, like ROAD2_CONF_TYPE = 'file' or 'object')
[ ] Find a solution for all 'directory' attributes inside the service.conf. All the other attributes are object compatible. There are files and directory for OSRM et Valhalla sources but it can't be different. It has to be files and directory locally.
[ ] Inside the docker provided by the project : rtest, ctest, utest, itest
[ ] Manually if necessary
[ ] Update the documentation
[ ] changelog.md
[ ] documentation directory
Code
Create a reader using promises/readFile for file, and use it everywhere in the code
Create getGlobalConfiguration() inside road2.js to handle the different parameters of the CLI. All parameters has to be read via nconf. They could be via -- or inside the ENV.
Need
The entire configuration is on a file-system. But it could be useful to have it inside an object storage.
Functionnalities
Tasks
Before coding
Code it
After or during coding
Code