-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade v2 kcl #4383
upgrade v2 kcl #4383
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (assuming you've tested in TEST
)
Seen on cropper (merged by @andrew-nowak 7 minutes and 36 seconds ago) Please check your changes! |
Seen on auth, collections, kahuna (merged by @andrew-nowak 7 minutes and 45 seconds ago) Please check your changes! |
Seen on image-loader, leases, media-api (merged by @andrew-nowak 7 minutes and 52 seconds ago) Please check your changes! |
Seen on usage (merged by @andrew-nowak 7 minutes and 56 seconds ago) Please check your changes! |
Seen on thrall (merged by @andrew-nowak 8 minutes and 2 seconds ago) Please check your changes! |
Seen on metadata-editor (merged by @andrew-nowak 8 minutes and 6 seconds ago) Please check your changes! |
What does this change?
The kinesis-client-library brings in a series of transitive dependencies with high vulnerability warnings. Upgrade to the latest in the v2 series to remove as many as possible with straightforward upgrades.
Further upgrades will be required in the near future, but we should follow the migration steps here https://docs.aws.amazon.com/streams/latest/dev/kcl-migration-from-2-3.html
How should a reviewer test this change?
Deploy to TEST, and upload or edit an image - check that the updates flow through the update stream to thrall and are persisted into the ES cluster.
How can success be measured?
Who should look at this?
Tested? Documented?