-
Notifications
You must be signed in to change notification settings - Fork 693
fix: support for AWS LegacyMd5Plugin #36408
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
Conversation
125c2e7
to
0bc6035
Compare
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.
❌ The new config flag is not set when the broker starts. Compare how S3BackupConfig
is built from broker config.
🔧 The new tests are good but I'd prefer a small amount of code duplication instead of having two classes (for legacy and latest) inherit from the parent. The test class structure is already a bit confusing, throwing in a new abstract class in the middle complicates this further.
@lenaschoenburg Isn't this how it's being parsed? I've run the The tests themselves are 99.9% the same that's why I've extracted them as a common base. I can have a second look on that. |
@panagiotisgts No you are right, I somehow missed that part during the review 👍 |
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.
Change itself looks good, please still consider adjusting the test as suggested.
0bc6035
to
2e3e8db
Compare
Successfully created backport PR for |
Successfully created backport PR for |
Description
Conditionally enable the AWS provided
LegacyMd5Plugin
to extend compatibility support for our backups with S3-compatible object storages. Ref. https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/s3-checksums.htmlChecklist
Related issues
closes #35953