Release v4.0.0 - Next-generation dynamic mapper

Overview

Based on feedback of an internal Hackathon we decided to totally refactor & rename the former MQTT Dynamic Mapper. This is exciting because it comes with great new features & functionality which goes beyond the purpose of the previous releases.

CAUTION: As the whole mapper has been redesigned it contains a lot of breaking changes. The easiest way to migrate from the "old" mapper to the new generation is to export your mappings, deploy the new mapper and import them again. Check the README.md for detailed description. Please recreate your connections after successful installation of the new generation mapper.

Let's find out what haven been changed!

What's Changed

• Full Multi-Tenancy support - We are now supporting out of the box multi-tenancy of Cumulocity IoT.
• Multiple message broker support - We are not limited to MQTT anymore. Any other message broker can be added, configured and used at the same time.
• Renaming - Due to the point above we removed "MQTT" from the name and packages to "Dynamic Mapper" only.
• Logging has been drastically improved not spamming irrelevant information anymore
• MQTT Connect support - We prepared and started the development of MQTT Connect which is a MQTT Broker provided by Cumulocity IoT.

Full Changelog: v3.3.4...v4.0.0