Esta página se tradujo automáticamente. Leer el original en inglés.

Component

core/ai-pipeline/temporal

Temporal, a durable-execution engine. A multi-step job is written as ordinary program code against one of the project's client libraries; the engine records every step's outcome as an event and hands the next piece of work to a worker the application itself deploys. Because the run is a replayable event history rather than a position in a process, a worker that crashes mid-job is replaced and the job resumes where it stopped, and a step that fails is retried on the policy the code declared. That division is what separates this from a scheduler: the engine owns the run's history and its timers, while the application owns the code each step executes. It keeps none of its own durable state. A relational datastore holds the event histories and a second database on that same connection holds the visibility index the console and the list APIs read, so the store is wired as a topology edge to a datastore component the Aggregate already declares rather than bundled inside this one. The engine is reached over gRPC on the frontend service, which is the address the provides contract publishes; a browser console is deployed alongside it. Realized on Kubernetes through a Helm Recipe that sources the project's own chart. It has no standalone local-container form, so no Compose Recipe is provided. Each of the engine's services serves its own metrics, in pods of its own, so the Recipe publishes the pod labels selecting every one of them, the name of their metrics port and the path, for a scraper that discovers those pods directly.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:60d848e16a196199e572a931bf940dc5c539909ce68a5fb35ed51a0c51fa1881
Publicado
2026-11-10T10:09:45Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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:b73cbac98a2f203410f5c676e05c155fa82c0f89872211a0655912026fe5d7fa

Referencia en esta versión

oci://hub.aggrega.ai/component/core/ai-pipeline/temporal:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
console_enabledbooleantruenoDeploy the browser console beside the engine. The console reads the visibility index to list and inspect runs; the engine serves its gRPC API with or without it, so turning it off removes a browser surface rather than a capability.
admin_tools_enabledbooleantruenoDeploy the administrative command-line image as a long-running pod an operator can exec into to inspect namespaces, describe a run, or apply a schema change. Turning it off removes that entry point; it serves no application traffic either way.

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
portinteger (min 1, max 65535)7233noPort the frontend service serves the gRPC API on. This is the address workers and clients dial, and the one the provides contract publishes. Most operators should omit this and let the Recipe assign the default (7233).
console_portinteger (min 1, max 65535)8080noPort the browser console listens on. It carries no application traffic; it exists so the console can be reached separately from the gRPC API.
history_shardsinteger (min 1)512noHow many shards the event history is partitioned across, which bounds how far the engine can scale out. It is fixed for the life of an installation — the engine cannot repartition an existing history, so raising it later requires a new installation. Size it for the load the installation is expected to reach rather than for its first day.
source_versionstring—noSource artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—síIn-cluster DNS name of the Service fronting the engine's frontend. A worker or a client that starts a run points its connection target at this name together with `port`.
portinteger—síTCP port that frontend accepts client connections on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
protocolstring—noHow the published address is spoken to — `grpc`, so a consumer configures one of the project's client libraries rather than an HTTP client.
metrics_pod_selectorstring—noKubernetes label selector matching the pods of every engine service, for a scraper that discovers those pods directly rather than scraping one address. Published beside `metrics_pod_port` and `metrics_path`.
metrics_pod_portstring—noName of the container port on those pods that carries the metrics, `metrics`.
metrics_pathstring—noPath the metrics are served at on that port, `/metrics`.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

metadata_store

Selector
component.aggrega.ai/category=datastore
Inyección
env

Slots que cada conexión a través de este socket puede llenar

SlotSelectorObligatorioInyecciónSensibleDescripción
credentialfeature.aggrega.ai/kind=secretno—síPassword the engine authenticates to the relational datastore this connection reaches with. When attached, the Recipe points the engine at the produced Secret so the value never appears in the rendered manifest. Unattached, the engine is configured with no password, which suits a store reached without one and matches what the standard-library relational Recipes leave in place when nothing is attached to them.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

No se declararon slots de acoplamiento.

Lista de permitidos de autoinyección

env

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad