-
Notifications
You must be signed in to change notification settings - Fork 1
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
Apply Aiven-specific changes on top of upstream 4.1.3 #21
Conversation
meatlink
commented
Oct 27, 2023
- changes related to .spec file were omitted, we do not need them anymore
- RF uptuning functionality were omitted, because now we have guardrails framework for that
The data will be provided by Astacus, streaming from other nodes is not necessary.
It's more convenient to set it there in Astacus. Option semantics is preserved, the value specified in Java properties has priority.
We decorate standard PasswordAuthenticator with a few platform specific features, that don't change the externally observable behavior - so it's absolutely compatible with PasswordAuthenticator. A few tools and client libraries do not support custom authenticators. For example: ZDM Proxy. They fail whenever they see anything but PasswordAuthenticator nevertheless they are in fact completely compatible. So we want to stop advertising our custom authenticator and pretend that it's a standard PasswordAuthenticator.
the 4.0.11 branch seems to have this commit 7372136 do we not need it here ? |
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.
requesting changes based on comment above
I'm trying the "assignee" workflow and arbitrarily assigned @sjamgade to this :-) |
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.
yay, CI passed