Repository navigation
Additional datasources now require XA - #32403
Conversation
There was a problem hiding this comment.
It's a little nuanced, but we can still support the case of aurora as the default datasource with a tweak to recommendation / check.
There was a problem hiding this comment.
It should also mention that you'll get a warning about recovery not being enabled, and likely mention that there isn't out-of-the box support via the operator.
There was a problem hiding this comment.
I don't think I noticed any warning.
Operator supports the .spec.transaction. xaEnabled field.
There was a problem hiding this comment.
Ah, I had forgotten that we set quarkus.transaction-manager.enable-recovery=true along with the other changes to disable XA by default - so there will be no warning. In that case we just need to document that recovery isn't supported when you don't have persistent storage for the transaction store which is especially true when using the operator.
There was a problem hiding this comment.
Added a note on the recovery.
There was a problem hiding this comment.
Added a note on the recovery.
We should expand on that with a WARNING and call out containerized / operator usage specifically. If it's not clear when the full xa features are not available, then this solution is not much better than setting the workaround flag.
cc @yrodiere
There was a problem hiding this comment.
@shawkins I wonder if we could do that as a follow-up. This change here is to just document the breaking change we did that XA is now required. The upgrading guide is IMHO not supposed to supplement a proper docs for additional datasources which will be added as part of #29116. On a side note, AFAIK, Quarkus itself doesn't provide such warning in their docs.
There was a problem hiding this comment.
I wonder if we could do that as a follow-up.
Sounds good.
On a side note, AFAIK, Quarkus itself doesn't provide such warning in their docs.
I agree https://quarkus.io/guides/transaction does not spell out the containerized scenario, but it seems like it could be less obvious or assumed to be turn-key when utilized via Keycloak so we should be clear about expectations.
There was a problem hiding this comment.
Added a comment in #29116 to remind us later.
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.forms.ResetPasswordTest#resetPasswordDisabledUserKeycloak CI - Forms IT (chrome) org.keycloak.testsuite.forms.ResetPasswordTest#resetPasswordTwiceInNewBrowserKeycloak CI - Forms IT (chrome) org.keycloak.testsuite.forms.ResetPasswordTest#resetPasswordWrongSmtpKeycloak CI - Forms IT (chrome) org.keycloak.testsuite.forms.ResetPasswordTest#resetPasswordExpiredCodeAndAuthSessionPerActionLifespanKeycloak CI - Forms IT (chrome) |
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.webauthn.WebAuthnPropertyTest#timeoutKeycloak CI - WebAuthn IT (chrome) org.keycloak.testsuite.webauthn.WebAuthnRegisterAndLoginTest#webAuthnPasswordlessAlternativeWithWebAuthnAndPasswordKeycloak CI - WebAuthn IT (chrome) |
Closes keycloak#32402 Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
Co-authored-by: Steven Hawkins <shawkins@redhat.com> Signed-off-by: Václav Muzikář <vaclav@muzikari.cz>
Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
Signed-off-by: Václav Muzikář <vmuzikar@redhat.com>
|
@vmuzikar - thank you for putting into this extra effort to have a well-defined error message with actionable instructions when there more than one non-XA datasource. This will make a great difference to users, so they don't need to figure out the cause and possible remedies! |
Closes #32402