amazon-kinesis-client 2.4.2 brings in a version of apache avro with a critical vulnerability - but that is the latest version of kcl that depends on a v1 of slf4j - easier to override the version of avro for now (if it works) than untangling the slf4j upgrade.
How should a reviewer test this change?
How can success be measured?
Who should look at this?
Tested? Documented?
[ ] locally by committer
[ ] locally by Guardian reviewer
[x] on the Guardian's TEST environment
[ ] relevant documentation added or amended (if needed)
All deployment options
- [Deploy build 12911 to TEST](https://riffraff.gutools.co.uk/deployment/deployAgain?project=media-service%3A%3Agrid%3A%3Aall&build=12911&stage=TEST&updateStrategy=MostlyHarmless&action=deploy)
- [Deploy parts of build 12911 to TEST by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=media-service%3A%3Agrid%3A%3Aall&build=12911&stage=TEST&updateStrategy=MostlyHarmless)
What does this change?
amazon-kinesis-client 2.4.2
brings in a version of apache avro with a critical vulnerability - but that is the latest version of kcl that depends on a v1 ofslf4j
- easier to override the version of avro for now (if it works) than untangling the slf4j upgrade.How should a reviewer test this change?
How can success be measured?
Who should look at this?
Tested? Documented?