Adding support for partial configuration definitions (e.g. like the common linux pattern ofconfig.d/directory which contains multiple configuration files treated as one logical configuration), would make it easier for new applications to add new entries into the tedge-configuration-plugin.toml and tedge-log-plugin.toml files.
There could be multiple ways to support registering new configuration and log file locations, either via MQTT or file based.
Scenario 1 - custom service which supports log and configuration files
A user develops a new service which is deployed as a linux package. The service writes logs files which the user would like to automatically register to the tedge-agent so that the cloud user can request the logs associated to the service. The same service also has configuration files which should be managed by thin-edge.io.
Adding support for partial configuration definitions (e.g. like the common linux pattern of
config.d/directory which contains multiple configuration files treated as one logical configuration), would make it easier for new applications to add new entries into thetedge-configuration-plugin.tomlandtedge-log-plugin.tomlfiles.There could be multiple ways to support registering new configuration and log file locations, either via MQTT or file based.
Scenario 1 - custom service which supports log and configuration files
A user develops a new service which is deployed as a linux package. The service writes logs files which the user would like to automatically register to the tedge-agent so that the cloud user can request the logs associated to the service. The same service also has configuration files which should be managed by thin-edge.io.