Skip to content
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

Merged
merged 5 commits into from
Nov 21, 2023

Conversation

meatlink
Copy link

  • 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.
@github-actions
Copy link

github-actions bot commented Oct 27, 2023

Unit Test Results

7 011 tests   6 958 ✔️  1h 22m 37s ⏱️
   846 suites       53 💤
   846 files           0

Results for commit 158a177.

♻️ This comment has been updated with latest results.

@alanfranz alanfranz requested a review from sjamgade November 15, 2023 11:44
@sjamgade
Copy link

the 4.0.11 branch seems to have this commit 7372136 do we not need it here ?

@alanfranz
Copy link

alanfranz commented Nov 17, 2023

the 4.0.11 branch seems to have this commit 7372136 do we not need it here ?

Yes, we need that or we'll get back to a vulnerable version. I'm surprised this wasn't fixed upstream. @meatlink

EDIT:
it's on the 4.1 branch upstream but they didn't do any release since July.

Copy link

@sjamgade sjamgade left a 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

@alanfranz
Copy link

I'm trying the "assignee" workflow and arbitrarily assigned @sjamgade to this :-)

Copy link

@sjamgade sjamgade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yay, CI passed

@sjamgade sjamgade merged commit bca8676 into aiven-4.1.3 Nov 21, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants