Component

core/ai-tool/event-publisher

A tool that lets an agent emit an event rather than call for a result, so a deployment can hand work off to whatever consumes the stream instead of waiting on a reply. The developer names the topic the event is published to, and may reference a schema the payload is expected to satisfy. It declares a required socket onto a message broker the deployment runs, so the broker it publishes to is resolved in the topology. Marked mutating: a published event is visible to its consumers and cannot be withdrawn. Realized on Kubernetes as a Knative Service: the control plane admits a call while the revision runs no replicas and sets the replica count from the concurrency it observes, so the tool occupies no compute between the calls that invoke it. It publishes the host, port, endpoint and protocol an agent reaches it on. The catalog pins no image, so nothing renders until the Release sets `infra.image`. The broker's address reaches the tool's code under default variable names; an `inject:` block on the connection delivers instead, as variables or files, the names that code reads. A broker serving TLS publishes a protocol saying so, and the connection's `server_ca` slot gives the tool the authority to check it against, as a mounted file. The component's own `inject:` block takes `env` and `file` entries too, and one reading a value of the tool alone replaces that value's default variable name.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:2e6c2c92df872cfe7c16b5d8a3e703879818bbae3d81d3a566246e25054c26c1
Published
2026-11-10T10:09:54Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:3c9c9f9a34b9eed955775b39198ca1cbeb310cec4847f7564a58e514f54eb0b5

Reference at this version

oci://hub.aggrega.ai/component/core/ai-tool/event-publisher:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

Extends BaseComponents#/schemas/BaseToolParameter

NameTypeDefaultRequiredDescription
target_topicstring—yes—
payload_schema_refstring—no—

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestring—noContainer image serving the tool over HTTP.
portinteger (min 1024, max 65535)8080noPort the tool listens on, and the port it publishes to consumers.
computeobject—no—
min_replicasinteger (min 0)0noReplica floor. Zero is what lets the tool run no replicas between the calls that invoke it.
max_replicasinteger (min 1)5noReplica ceiling the realization's autoscaler may reach.
control_plane_presentbooleanfalsenoOperator affirmation that the Knative Serving control plane the realization needs is installed in the target cluster. The build halts unless this is set true, so a custom resource is never emitted as an orphan into a cluster that cannot reconcile it.
overridesobject (open)—noRealization-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-cluster DNS name an agent calls to emit an event. A consumer that composes its own address dials this name; one that does not reads `endpoint` instead.
portinteger—yesTCP port the publish request is accepted on. The realization fronts the tool on the control plane's own port rather than the tool container's, so a consumer reads this rather than the port an operator set.
endpointstring—yesFull base URL an agent posts an event to, with the host and the port already composed. A consumer hands it to its tool client as the address it calls.
protocolstring—noURL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

target_messaging

Selector
component.aggrega.ai/category=messaging, component.aggrega.ai/type in (server, stateful-server)
Inject
env, file

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
server_cafeature.aggrega.ai/kind=secretnofileyesOptional authority the tool's container checks the broker's certificate against while the broker serves TLS, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only into the tool's container and delivers EVENT_TOOL_BROKER_SERVER_CA_FILE naming the file, on a connection writing an inject block too; checking the certificate against it is the container's. The build halts on a server_ca publishing no Secret name, on one wired to a broker publishing a protocol served without TLS — kafka, amqp, nats, ws or sip — and on one held on more than one connection. Fill it with core/referenced-secret mapped to helm/k8s-existing-secret, naming a Secret the namespace already holds.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

env, file

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy