Closed andrew-nowak closed 1 week ago
Seen on image-loader (merged by @andrew-nowak 7 minutes and 34 seconds ago) Please check your changes!
Seen on auth (merged by @andrew-nowak 7 minutes and 39 seconds ago) Please check your changes!
Seen on collections, media-api (merged by @andrew-nowak 7 minutes and 49 seconds ago) Please check your changes!
Seen on metadata-editor, usage (merged by @andrew-nowak 7 minutes and 55 seconds ago) Please check your changes!
What does this change?
We're using an old version of kcl-akka-stream, which was only ever released to bintray and so was committed directly into the repository when bintray was removed (see #3283). The earliest version of kcl-akka-stream that was released to Maven central is 4.1.1, which depends on kinesis-client-lib 2.x. Upgrade both together, to get onto a version which is both a) on Maven central and b) compatible with scala 2.13.
Note however that kcl-akka-stream is no longer maintained, and a Pekko alternative has not been created (see https://github.com/StreetContxt/kcl-akka-stream/issues/191) which will be an annoyance for a Play 3.0 upgrade. (Technically it isn't required that we remove all usages of Akka to upgrade to Play 3.0, but it'd be very very nice if we could). To be dealt with at a later date.
Note also that this doesn't upgrade the version of the kinesis-client-library used in usage, since that uses rxscala (also no longer maintained) instead of Akka, so doesn't make use of kcl-akka-stream.
How should a reviewer test this change?
kcl-akka-stream is only used by Thrall - so try making some changes to data, or upload images etc. and check that the updates flow through to Thrall, which will then apply those updates onto the Elasticsearch index.
Tested? Documented?