You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue relates to #17Improve message handler pluggability.
Some message handler specific settings are directly put into the config.AzureSettings structure - MessageMapperConfig, AllowedLocalTopicsList, AllowedCloudMessageTypesList.
These settings are only for the message handling and they have nothing to do with the rest of the common settings, needed to establish and maintain connections toward Azure IoT Hub, local brokers, log settings, etc. Additionally, these apply only for the concrete binary of the Kanto azure connector, the default one will need settings for its passthrough handlers, while extended/customized binaries may add new handler settings and may not need any of the default passthrough settings.
As the #17 proposal is to move full message handler instantiation control to main package, then it is better to move message handlers settings there too. E.g. define a new settings structure, that holds all the settings for the message handlers that will be created and extend the common config.AzureSettings with it; respectively the message handler flags should be defined and processed by main package too.
The text was updated successfully, but these errors were encountered:
stoyan-zoubev
changed the title
Decoupd common Azure connector settings from message handlers' settings
Decouple common Azure connector settings from message handlers' settings
Oct 11, 2022
[#19] Decouple common Azure connector settings from message handlers' settings
- AzureSettings struct contains only general azure connector settings
- message handlers' specific settings and flags (e.g.passthrough topics) moved to cmd/azure-connector/config.go file
Signed-off-by: Stoyan Zoubev <[email protected]>
This issue relates to #17 Improve message handler pluggability.
Some message handler specific settings are directly put into the
config.AzureSettings
structure -MessageMapperConfig
,AllowedLocalTopicsList
,AllowedCloudMessageTypesList
.These settings are only for the message handling and they have nothing to do with the rest of the common settings, needed to establish and maintain connections toward Azure IoT Hub, local brokers, log settings, etc. Additionally, these apply only for the concrete binary of the Kanto azure connector, the default one will need settings for its passthrough handlers, while extended/customized binaries may add new handler settings and may not need any of the default passthrough settings.
As the #17 proposal is to move full message handler instantiation control to
main
package, then it is better to move message handlers settings there too. E.g. define a new settings structure, that holds all the settings for the message handlers that will be created and extend the commonconfig.AzureSettings
with it; respectively the message handler flags should be defined and processed bymain
package too.The text was updated successfully, but these errors were encountered: