Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple common Azure connector settings from message handlers' settings #19

Closed
stoyan-zoubev opened this issue Sep 19, 2022 · 0 comments · Fixed by #33
Closed

Decouple common Azure connector settings from message handlers' settings #19

stoyan-zoubev opened this issue Sep 19, 2022 · 0 comments · Fixed by #33
Assignees
Labels
task Single unit of work
Milestone

Comments

@stoyan-zoubev
Copy link
Contributor

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 common config.AzureSettings with it; respectively the message handler flags should be defined and processed by main package too.

@e-grigorov e-grigorov added the task Single unit of work label Sep 19, 2022
@e-grigorov e-grigorov moved this to Todo in Eclipse Kanto Sep 19, 2022
@konstantina-gramatova konstantina-gramatova added this to the M3 milestone Sep 29, 2022
@stoyan-zoubev 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
@stoyan-zoubev stoyan-zoubev moved this from Todo to In Progress in Eclipse Kanto Oct 14, 2022
stoyan-zoubev added a commit to SoftwareDefinedVehicle/kanto-azure-connector that referenced this issue Oct 14, 2022
…eneral azure connector 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]>
@stoyan-zoubev stoyan-zoubev moved this from In Progress to Ready for Review in Eclipse Kanto Oct 14, 2022
@e-grigorov e-grigorov moved this from Ready for Review to In Review in Eclipse Kanto Oct 17, 2022
@e-grigorov e-grigorov moved this from In Review to In Progress in Eclipse Kanto Oct 19, 2022
@e-grigorov e-grigorov moved this from In Progress to In Review in Eclipse Kanto Oct 24, 2022
e-grigorov pushed a commit that referenced this issue Oct 24, 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]>
Repository owner moved this from In Review to Done in Eclipse Kanto Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Single unit of work
Projects
Status: Done
3 participants