Skip to content

History

Revisions

  • push-ingress: live Google OIDC signature validation (ai-meta#91)

    @kadyapam kadyapam committed Jun 12, 2026
    a3806b3
  • docs: push-ingress (POST /ingress/{listener}) page — verify→forward, auth-gated directives (#90 Phase 3)

    @kadyapam kadyapam committed Jun 12, 2026
    64534ec
  • wiki: GET /sharding/preview diagnostic endpoint (Phase F R3b-2) Per wiki-maintenance.md Rule 2a, route docs land in lockstep with the code (noetl/gateway#25 + the v3.2.0 PR). New subsection under "NoETL shard map" with the route shape, response example, validation rules, wire contract with noetl-server, and the deliberate exclusion from the /noetl/* proxy catchall and auth middleware. Refs noetl/ai-meta#49 Refs noetl/gateway#25

    @kadyapam kadyapam committed Jun 4, 2026
    f0c6c02
  • wiki: events routes now shard-routed via body parsing (Phase F R3a-2) Per wiki-maintenance.md Rule 2a, env-shaped behavior docs land in lockstep with the code (noetl/gateway#23 + the v3.1.0 PR). - Routes covered list split into two subsections: path-param (R3a) and body-param (R3a-2). - POST /noetl/events + /events/batch moved from "Routes NOT covered" to "Routes covered (body-param)". - R3a-2 deferral note removed. Refs noetl/ai-meta#49 Refs noetl/gateway#23

    @kadyapam kadyapam committed Jun 4, 2026
    959caae
  • wiki: configuration gains NoETL shard map section (Phase F R3a) Per wiki-maintenance.md Rule 2a, env-shaped config docs land in lockstep with the code (noetl/gateway#20 + the v2.10.0 PR). - `NOETL_BASE_URL` row clarified to call out the shard-map fallback behavior. - New "### NoETL shard map (Phase F R3a)" subsection: - TOML config shape ([[noetl.shards]] with shard_index + base_url). - Startup constraints (indices contiguous 0..N-1, no duplicates, no holes; gateway panics on a bad map). - Routes covered by R3a (path-param execution_id) vs not covered (body-param → R3a-2; commands → R3b; cluster-wide → any shard answers). - Hash function + wire contract with noetl-server's src/sharding.rs::shard_for. Refs noetl/ai-meta#49 Refs noetl/gateway#20

    @kadyapam kadyapam committed Jun 4, 2026
    543d7d1
  • wiki(gateway): finish Round 03 cleanup — architecture / deployment / configuration Round 03 of noetl/ai-meta#23 removed the firestore_subscriptions subsystem from the gateway code (noetl/gateway#18 + #19) and this wiki's subscriptions.md was already converted to a historical reference at noetl-gateway-wiki@4356945. But three other pages still described the removed surface as live behaviour: - architecture.md: the position-in-stack diagram listed /api/subscriptions/firestore as a current gateway capability; the playbook_state.rs section omitted calendar.event.touched from FORWARDED_EVENT_TYPES; firestore_subscriptions.rs had a dedicated current-module description; the request-flow example showed the removed subscription path. Replaced the diagram + arrows, expanded FORWARDED_EVENT_TYPES to include calendar.event.touched, converted the firestore_subscriptions.rs section to a "Removed in v2.12.0" callout with a noetl/gateway#18 + #19 reference, replaced the subscription request-flow example with the new calendar.event.touched push-driven flow. - deployment.md: the container-image section said the image bundles a Python Firestore listener sidecar; the k8s manifests section said the gateway uses a sidecar pattern; there was a dedicated Firestore credential-provisioning section; /health spoke of the sidecar's IPC handle. All removed; image-size + build-time win from #19 noted in the history callout. - configuration.md: residual references in the "Postgres / NATS / Firestore credentials come from k8s Secrets" and "gateway's env only carries Postgres, NATS, Firestore service account" lines. Both dropped. Codex's earlier subscriptions.md → historical conversion + configuration.md "removed in v2.12.0" + sse-events.md FORWARDED_EVENT_TYPES table + Home.md release notes are all unchanged. Refs noetl/ai-meta#23 (Round 03 wiki finish).

    @kadyapam kadyapam committed May 29, 2026
    9fb6c56
  • wiki(gateway): document SSE forwarded-event-types + remove firestore_subscriptions

    @kadyapam kadyapam committed May 29, 2026
    4356945
  • wiki: bootstrap gateway wiki — v2.11.0 SSE subscriptions + lifecycle frames Adds six developer-facing pages covering the gateway's role, SSE channel, the new subscription endpoint and Python Firestore sidecar (v2.11.0), env configuration, and deployment. Pages: - Home.md: what the gateway owns vs does not own, page index. - _Sidebar.md: navigation. - architecture.md: module map (auth, graphql, sse, callbacks, playbook_state, firestore_subscriptions, request_store, proxy, session_cache); request-flow examples for authenticated execution, Firestore subscription, and lifecycle push. - sse-events.md: GET /events channel, full frame catalog (message init, ping, playbook/result, playbook/progress, playbook/state in v2.11.0, subscription/event in v2.11.0), payload schemas, reconnection notes. - subscriptions.md: POST/DELETE /api/subscriptions/firestore, the Python sidecar architecture (one process per pod, JSON-line IPC), credential provisioning recipe, what the endpoint is not (no writes, no replacement for security rules). - configuration.md: env var reference grouped by concern; classification of what is platform-runtime vs business-logic per the secrets-and-credentials rule. - deployment.md: build (cargo, container, crate), k8s manifests, Firestore credential provisioning, Cloudflare Tunnel, health checks, roll forward / back. Cross-links to the ephemeral_blueprints architecture doc, the ops wiki for the GKE install, and the travel wiki for the consumer side.

    @kadyapam kadyapam committed May 24, 2026
    b98c7e8
  • Initial Home page

    @kadyapam kadyapam committed May 24, 2026
    7c7c78d