Skip to content

fix: use KC_HTTP_RELATIVE_PATH in Keycloak health check URL#988

Open
themavik wants to merge 1 commit intotestcontainers:mainfrom
themavik:fix/964-keycloak-health-relative-path
Open

fix: use KC_HTTP_RELATIVE_PATH in Keycloak health check URL#988
themavik wants to merge 1 commit intotestcontainers:mainfrom
themavik:fix/964-keycloak-health-relative-path

Conversation

@themavik
Copy link

Summary

Fixes #964.
Root cause: Health check URL was hardcoded to /health/ready without considering the KC_HTTP_RELATIVE_PATH environment variable.
Fix: Prepend the configured relative path to the health check endpoint URL.

Changes

  • Updated Keycloak container health check to use configured relative path
  • Added http_relative_path parameter and with_http_relative_path() fluent method
  • Updated get_url() to include relative path for KeycloakAdmin client

Testing

  • Verified fix addresses reported 404 scenario with relative path
  • Change is minimal and follows existing code patterns

Made with Cursor

…ainers#964)

Root cause: Health check URL was hardcoded to /health/ready without
considering the KC_HTTP_RELATIVE_PATH environment variable.

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Keycloak health check not working with HTTP relative path

1 participant