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
quarkus-next: Replace deprecated QUARKUS_PROFILE_PROP constant #29439
Conversation
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.saml.ArtifactBindingWithResolutionServiceTest#testReceiveArtifactNonExistingClient
|
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.
Unreported flaky test detected, please 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.
LGTM
Closes: keycloak#29438 Signed-off-by: Peter Zaoral <pzaoral@redhat.com>
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
Closes: #29438
I decided to determine the property name/key based on the launch mode, which means it can be either
quarkus.profile
(for prod and dev mode) orquarkus.test.profile
(for test mode).I think this approach is in alignment with the Quarkus guidelines. Otherwise, if we would like to stick with a constant, it can be done via
LaunchMode.NORMAL.getProfileKey()
.cc: @vmuzikar @shawkins