This adds a method to translate the type returned from the lambda event record to the object type that the kinesis client library is expecting.
As of version 3.0.0 of aws-lambda-java-events reading records from the lambda event returns a different model to the one that the kinesis client library deaggregation method is expecting.
According to the amazon docs we should be importing a custom deaggregation library for running in a lambda. However, the library is not officially supported by AWS and the version we require is not available on maven. See this issue for more information.
I think this approach is our best option to enable us to be able to upgrade aws libraries
How to test
Tested on CODE that publishing an article in CAPI results in log statement produced in thenotification app which says: ContentNotification
What does this change?
This adds a method to translate the type returned from the lambda event record to the object type that the kinesis client library is expecting.
As of version 3.0.0 of aws-lambda-java-events reading records from the lambda event returns a different model to the one that the kinesis client library deaggregation method is expecting.
According to the amazon docs we should be importing a custom deaggregation library for running in a lambda. However, the library is not officially supported by AWS and the version we require is not available on maven. See this issue for more information.
I think this approach is our best option to enable us to be able to upgrade aws libraries
How to test
Tested on CODE that publishing an article in CAPI results in log statement produced in the
notificationapp which says:ContentNotificationHow can we measure success?
Have we considered potential risks?
Images
Accessibility