-
-
Notifications
You must be signed in to change notification settings - Fork 8
[Merged by Bors] - fix/ldap-secret-key-name #362
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
I'm attempting a CI run: https://ci.stackable.tech/view/02%20Operator%20Tests%20(custom)/job/trino-operator-it-custom/44/ Edit: I already saw that it failed ... I don't really know why. :( |
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.
Feel free to ignore ;)
Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.de>
Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.de>
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 when tests succeed
Please also add a CHANGELOG entry (it's a breaking change) |
Already did! |
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.
Sorry, hadn't refreshed
Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.de>
The test is green!! 🎉 |
bors merge |
# Description This PR fixes the inconsistency of Trino with Superset and NiFi. While Superset and NiFi use "user" and "password" for the LDAP Secret keys, Trino just used it's environment variable names. Co-authored-by: Felix Hennig <fhennig@users.noreply.github.com>
Pull request successfully merged into main. Build succeeded: |
This is no CRD change, right? But is it a breaking change otherwise? Like...will the new operator work with old deployments or require a restart or any other work? |
Yes it's breaking. If a user used Trino with LDAP he needs to update his Secret containing the bind credentials. |
In that case we should at least have a changelog entry for this. @fhennig could you please add that? |
The changelog entry was added in this PR ;)
|
Thanks! Not sure how I missed that |
Description
This PR fixes the inconsistency of Trino with Superset and NiFi. While Superset and NiFi use "user" and "password" for the LDAP Secret keys, Trino just used it's environment variable names.
Review Checklist
Once the review is done, comment
bors r+
(orbors merge
) to merge. Further information