fix(dev-env): correct Keycloak healthcheck port and migrations auto-apply doc - #4170
Open
jdavidroberts wants to merge 2 commits into
Open
fix(dev-env): correct Keycloak healthcheck port and migrations auto-apply doc#4170jdavidroberts wants to merge 2 commits into
jdavidroberts wants to merge 2 commits into
Conversation
Keycloak 26 moved health endpoints to a separate management interface on port 9000 by default (see the started-server log: Management interface listening on http://0.0.0.0:9000). The healthcheck was probing /health/ready on the main port 8080, which 404s, so the container always reported unhealthy even though Keycloak started fine. Set KC_HEALTH_ENABLED and point the probe at port 9000; verified it now flips to healthy within a few retries. Signed-off-by: David Roberts <david.jdr.roberts@gmail.com>
migrations/ was documented as auto-applied on relay startup, but BUZZ_AUTO_MIGRATE defaults to false (see TESTING.md and main.rs). Local dev applies migrations via just migrate/just setup, and the relay skips its embedded migration step unless the flag is explicitly on. Only the Helm chart deploy defaults it to true. Noticed this while setting up a fresh clone: the relay boot log clearly said migrations were being skipped, which did not match the doc. Signed-off-by: David Roberts <david.jdr.roberts@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
instead of the main port (8080), where /health/ready 404s.
"auto-applied on relay startup" by default — BUZZ_AUTO_MIGRATE defaults
to false, and local dev applies them via
just migrate/just setup.Why
Ran into both while onboarding a fresh clone. Keycloak reported "unhealthy"
in
docker compose psdespite starting fine — Keycloak 26 moved healthendpoints to a separate management interface on port 9000 by default, so
the existing healthcheck (written for port 8080) always 404'd. Separately,
the relay's boot log said "Skipping database migrations because
BUZZ_AUTO_MIGRATE is not enabled," which contradicted the repo-structure
doc.
Note: I also found stale
TYPESENSE_*vars in the root.env.exampleduring this pass, but that's already covered by #2555, so I left it out
here to avoid duplicating that effort.
Testing
docker compose up -d keycloak— container now reportshealthywithin~15s (previously stayed
unhealthyindefinitely)docker compose config --quiet— validatesjust ci— full local gate passes (fmt, clippy, unit tests, desktopbuild, Tauri check, mobile tests — 1022 mobile tests passed)
Searched open/closed PRs and issues for "keycloak", "typesense", and
"BUZZ_AUTO_MIGRATE" — no overlap besides #2555 noted above.
🤖 Generated with Claude Code