Skip to content

Expose Undertow OpenAPI discovery at the shared origin - #211

Open
beepboop2025 wants to merge 1 commit into
mainfrom
fix/undertow-origin-openapi-20260906
Open

Expose Undertow OpenAPI discovery at the shared origin#211
beepboop2025 wants to merge 1 commit into
mainfrom
fix/undertow-origin-openapi-20260906

Conversation

@beepboop2025

@beepboop2025 beepboop2025 commented Sep 6, 2026

Copy link
Copy Markdown
Owner

Root OpenAPI discovery currently returns 404 on api.seiche.info. Add an exact /openapi.json alias to the existing Undertow-generated schema at /undertow/x402/openapi.json so 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_SOURCE installer 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.json and 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.

@coderabbitai

coderabbitai Bot commented Sep 6, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: bef944a5-0147-41b6-a548-2a6998aa5dd2


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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.

1 participant