Repository navigation
consolidating profile logic and moving reaug related logic - #38514
Conversation
8128ee3 to
88920db
Compare
831063c to
cbeee84
Compare
cbeee84 to
682abcf
Compare
682abcf to
cea0704
Compare
3f34f52 to
aab109d
Compare
|
@keycloak/cloud-native this stops short of what is described in #38581 (comment) - while the changes don't lead to a reduction in line count, they do start to make Picocli less of a monolith and aggregate the code in hopefully a more understandable way. The downsides at this point are:
Both of these concerns could be removed if we adopt #38581 (comment) Also we'll ideally eventully pare back the usage ConfigArgsConfigSource.parseConfigArgs more - the ParseResult we're getting from picocli is enough give us the unmatched parameters, which we can then treat as our PropertyMapper / cli options - with no guess work as to what are command names / pico cli options. |
3513998 to
3d36dad
Compare
3d36dad to
f91aa2a
Compare
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.actions.TermsAndConditionsTest#termsAcceptedorg.keycloak.testsuite.actions.TermsAndConditionsTest#termsDisabled |
f91aa2a to
7488c80
Compare
16ec5e0 to
bf9c3ac
Compare
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.cluster.RealmInvalidationClusterTest#crudWithFailover |
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.cluster.RealmInvalidationClusterTest#crudWithFailover |
moves more logic onto the commands closes: keycloak#38581 Signed-off-by: Steve Hawkins <shawkins@redhat.com>
9b370fe to
634a4c7
Compare
|
Fully rebased. |
There was a problem hiding this comment.
LGTM, thank you for the updates!
This is a follow up to #38236 - after trying to add a test via PicocliTest for the hostname-strict-https check, it was clear that our current way of emitting the warning handling profiled properties wasn't consistent.
also aggregated the various places that were setting the profile to a single place
closes: #38581