#58 Keycloak - Connection Error - Fix #60
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
adrianliz
force-pushed
the
keycloak_connection_error
branch
4 times, most recently
from
29291cc
to
9c3cd67
Compare
adrianliz
force-pushed
the
keycloak_connection_error
branch
from
9c3cd67
to
36f6d00
Compare
|
@valentinacupac Could you take a look at this? Thanks! |
|
Thanks a lot @adrianliz! I am looking at it now... P.S. I saw in the logics above that "force-pushed the head branch yesterday" - were there any push issues that occurred, did you update to latest version of main before pushing, or it was something else... |
|
I saw it passed on GitHub Actions, so merged now... I will also test locally. |
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.
Changes:
src/main/resources/keycloak/realm-export.json)docker-compose.ymlci.ymlto usedocker-compose.ymlinstead of custom services