Expose Undertow OpenAPI discovery at the shared origin - #211
Open
beepboop2025 wants to merge 1 commit into
Open
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Root OpenAPI discovery currently returns 404 on api.seiche.info. Add an exact
/openapi.jsonalias to the existing Undertow-generated schema at/undertow/x402/openapi.jsonso the current Agentcash discovery parser can find the Undertow subset on this shared origin.Validation: the deployed Caddy 2.6.2 binary adapted the candidate and validated it in an isolated process. A precedence-aware comparison checked 50 route arrays: all 141 potentially overlapping pairs retain their relative order, and every reordered pair has provably disjoint matchers. Fifteen focused Caddy installer, rollback and edge tests passed. The only source change is seven added lines in
ops/Caddyfile.Maintenance condition: keep this PR unmerged while the signed v0.12.4 release remains the main publication identity. The existing catalog descendant gate rejects an ops-only successor; merging it alone would break scheduled full-site publication. Main and scheduled publishers remain unchanged. A separately signed edge tag may be applied through the existing
SEICHE_CADDY_SOURCEinstaller override only after the repaired Undertow application passes live validation. Its immutable artifact, base hash, patch and rollback source are retained separately from the application checkout.Before the next ordinary Seiche application/edge deployment, incorporate this patch into the next fully signed and validated application release (including required publication receipts), or explicitly preserve the reviewed edge source override. The installer defaults to the application checkout and would otherwise remove this alias. The runtime source poller is currently masked; this operational artifact does not change that state. The Seiche Railway application remains on its accepted runtime release.
Operational activation: the separately signed edge artifact was accepted live on 6 September 2026 at 00:49 UTC. Root
/openapi.jsonand the nested Undertow schema returned identical bytes; the pinned Agentcash 1.7.5 parser found ten same-origin endpoints. Existing route priority, private-route rejection, Seiche v0.12.4 deployment identity and Undertow service processes were preserved. The immutable rollback source and installer backup remain retained. This PR remains unmerged under the maintenance condition above.