-
Notifications
You must be signed in to change notification settings - Fork 608
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
Upgraded to version 25.0.0 of Keycloak #770
Conversation
Can be internal port parametrized to be compatible with previous Keycloak versions? (just an idea) |
Yep, sounds good, and think my latest commit should fix it. I kept the http-internal port there for all cases, since it shouldn't matter if an extra port is exposed, although not used. |
Seems like the lint tests failed during the test setup. |
Hey there, I just received access to this Repo and will look at the failing Pipeline later today or tomorrow |
Hey, I updated the failing job to the newest version in #772, could you rebase your branch, and we will see if it works now? |
Yes, rebased now and it seems to work, and thanks. |
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.
Can you look at the Pipeline? It look like further adjustments are required for the new Version.
Signed-off-by: Hans Erik Heggem <[email protected]>
Signed-off-by: Hans Erik Heggem <[email protected]>
Signed-off-by: Hans Erik Heggem <[email protected]>
Signed-off-by: Hans Erik Heggem <[email protected]>
Signed-off-by: Hans Erik Heggem <[email protected]>
Great to see support for v25. Thanks a lot. Please create a release. |
Upgraded to version 25.0.0 of Keycloak. Tested in separate systems, and only change needed was to use the new internal 9000 port for health checks and metrics.