What's Changed
!! Breaking Change !!
Caution this release contains breaking changes which makes it necessary to migrate existing mappings! For details please read on.
- The format used for serializing the mappings was changed. We provide a migration script which helps to you convert the existing mappings to the new format #291
- The script uses go-c8y-cli. Make sure you have set it up and using a session pointing to your Cumulocity Tenant where the mappings should be migrated
- Make sure the script has valid permission to be executed on your system. Otherwise add
chmod +x dynamic-mapping-mgmt.sh - Run script:
dynamic-mapping-mgmt.sh migrateMappings- Changed display names of options and mappings type to more user friendly names: PROCESSOR_EXTENSION_SOURCE to Extension Source
- Additional mapping type Extension Source Target, Mapping handles payloads in custom format. In contrast to the Extension Source the completed processing of the payload: extract values from the incoming payload and then transform this to a Cumulocity API call. This requires that a custom processor extension in Java is implemented and uploaded through the "Processor extension" tab.
- Add connectors to left side navigation, under Configuration -> Connectors -> <CONNECTOR #1>, <CONNECTOR #2>, ...
- Add view to see event/errors logged by the mapping micro-service, under Monitoring -> Tab Mapping service events. This is helpful in cases where.a mapping could not be successfully loaded
- Migration jsonata4Java -> dashjoin jsonata #293
- Migration Cumulocity SDK 1020.155.0, JDK 21, spring boot 3.3.5
- Add testcases (junit, mockit): ConnectorConfigurationComponentTest , MappingTreeTest, JsonataDashJoinLibTest
- Scaling improvements by using mainly virtual threads where possible supported by Spring Boot & Java 21+.
Bugfixes
Full Changelog: v4.6.1...v4.7.0