feat: dedicated portal listener and stable presence reads - #457
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #457 +/- ##
==========================================
- Coverage 87.53% 87.49% -0.04%
==========================================
Files 400 400
Lines 265327 265628 +301
==========================================
+ Hits 232246 232405 +159
- Misses 33081 33223 +142 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
The portal now runs on its own listener per node instead of sharing the REST port behind a Host header check: the REST root always redirects to the Swagger UI, unknown API paths return plain 404 instead of SPA HTML, and the portal serves the SPA at its own origin. Stale realm presence reads now wait for the in-flight refresh before answering, which removes the periodic flapping of healthy peers to "configured" in realm views. The local cluster deploy prints a reworked summary with labeled per node URLs and test credentials. Enabling the portal now requires PORTAL_SOCKET_ADDRESS and API_PUBLIC_URL, the portal CSP derives the API origin automatically, and CORS_ALLOWED_ORIGINS must include the portal origin.
Changes: