Dev/mip 14/config files restructure
Created by: ThanKarab
Following the MIP-14 ticket the following changes were made:
- Decoupled the node_catalog and the node config file variables.
- Split the mipengine config files into one per service (controller, node).
- Node config file location can now be provided as env variable.
- The Node is now providing it's data to the node_catalog. The node_catalog does NOT need to be manually altered.
- Deployment scripts were changed and follow a new logic:
- A
.deployment.toml
file can be created from the developer following a template. - The
inv create_node_configs
task is then executed to create the config files in the.../configs/nodes/
folder from the.deployment.toml
file. - The
inv deploy --start-all
task will then setup everything based on the config files. - There is also the
inv start_node --node localnode1
command that will restart a node service, using the appropriate config file.
- A
- More deployment script refactoring.