Bump Keycloak version to 17.0.1 #24559
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
quarkus-bot
bot
added
area/dependencies
gsmet
approved these changes
Mar 25, 2022
|
Thanks @gsmet took me only 2 days to fix it :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a try number 2 at bumping the Keycloak version to 17.0.1.
integration-tests/container-imagetests were failing in Native, in the end adding--hostname-portin the shared network case resolved theissuermismatch issue - it is a test issue only,17.0.1might've done some extra changes related to it.I've also added a check that the realm is available after it has been created - it is not what makes the tests pass - but it would not harm I guess