Managed Trigger extensions
How StreamNative Cloud extends the Trigger API in Orca Agent Engine with messaging sources and session modes.
A managed Trigger extension is a StreamNative Cloud capability on the same /v1/triggers routes as
the portable Trigger API. It does not create an agenttriggers extension group.
The generated Trigger operation pages show the portable core contract. Send Cloud-only source types, session modes, and replica counts only to StreamNative Cloud.
Portable and Cloud fields
| Field | Portable core | StreamNative Cloud |
|---|---|---|
source.type | cron | cron, kafka, pulsar |
session_mode | SESSION_PER_EVENT | SESSION_PER_EVENT, SESSION_PER_TOPIC, SESSION_PER_KEY, SHARED |
| Cron session modes | SESSION_PER_EVENT | SESSION_PER_EVENT, SHARED |
replicas | Exactly 1 | Positive integer |
GET /v1/triggers include_archived | Declared | Not supported |
Write-operation idempotency-key header | Declared | Not supported |
Kafka and Pulsar source variants require a connection and support topic-selection fields. The Cloud
overlay is the source of truth for complete fields and required combinations.
Source of truth
apis/registry-api/managed-agents.yaml contains the portable core contract. The Cloud deployment overlay lives in
apis/registry-api/managed-agents-deployment.overlay.yaml, vendored from
orca-sdk-typescript commit 8657ccab. Review both files together when updating a trigger example
or generated client.
The overlay changes request and response schemas without changing the route. A deployment that implements only the portable cron subset returns its normal API error for Cloud-only values.