We're trying to make things as consistent and clear as possible in terms of where information is configured and stored. In particular, things which can (or should be) configured in the project8_authentications.json file are at times currently present in config files (main examples being broker hostname for AMQP, and possibly database details).
From slack discussion, the consensus seems to be that it is better to have everything read a broker from the auth file, not the config file. We will need to decide if the value in a config file should be ignored, or if it should override the value from the auth file (the command line flag will still override anything else). This may be confusing because the value in the existing config files would be meaningless and we'd need to be sure to remove that everywhere, but having multiple files which can configure the same parameter is also confusing.
Current plan is to think about it and then try to better define what goes where and how things are treated. Discussion or thoughts can go here, changes will need to be implemented in dripline-xxx.
guiguem
commented
7 years ago
We're trying to make things as consistent and clear as possible in terms of where information is configured and stored. In particular, things which can (or should be) configured in the project8_authentications.json file are at times currently present in config files (main examples being broker hostname for AMQP, and possibly database details).
From slack discussion, the consensus seems to be that it is better to have everything read a broker from the auth file, not the config file. We will need to decide if the value in a config file should be ignored, or if it should override the value from the auth file (the command line flag will still override anything else). This may be confusing because the value in the existing config files would be meaningless and we'd need to be sure to remove that everywhere, but having multiple files which can configure the same parameter is also confusing.
Current plan is to think about it and then try to better define what goes where and how things are treated. Discussion or thoughts can go here, changes will need to be implemented in dripline-xxx.