Esta página foi traduzida automaticamente. Ler o original em 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.

Proveniência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como editor oficial.
Digest do conteúdo
sha256:60d848e16a196199e572a931bf940dc5c539909ce68a5fb35ed51a0c51fa1881
Publicado
2026-11-10T10:09:45Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • 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

Referência nesta versão

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

Parâmetros do programador

Valores que o programador define no Aggregate.

NomeTipoPredefiniçãoObrigatórioDescrição
console_enabledbooleantruenãoDeploy 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_enabledbooleantruenãoDeploy 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.

Dimensionamento do operador

Dimensionamento da infraestrutura que o operador ajusta por ambiente.

NomeTipoPredefiniçãoObrigatórioDescrição
portinteger (min 1, max 65535)7233nãoPort 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)8080nãoPort 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)512nãoHow 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—nãoSource artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility.
computeobject—não—
overridesobject (open)—nãoProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrato de saída

Valores que este componente publica para os consumidores através da topologia uses.

NomeTipoPredefiniçãoObrigatórioDescrição
hoststring—simIn-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—simTCP 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—nãoHow 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—nãoKubernetes 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—nãoName of the container port on those pods that carries the metrics, `metrics`.
metrics_pathstring—nãoPath the metrics are served at on that port, `/metrics`.

Sockets uses

Os sockets de dependência através dos quais este componente se liga. O destino de cada ligação estabelecida através de um socket tem de satisfazer o respetivo seletor de etiquetas, e cada ligação pode transportar um acoplamento nos slots que o socket declara. Cada ligação que o Aggregate ou a Release estabelece através do socket tem de preencher os slots obrigatórios.

metadata_store

Seletor
component.aggrega.ai/category=datastore
Injeção
env

Slots que cada ligação através deste socket pode preencher

SlotSeletorObrigatórioInjeçãoSensívelDescrição
credentialfeature.aggrega.ai/kind=secretnão—simPassword 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 acoplamento

Pontos de vinculação com nome nos quais uma Feature se acopla a este componente. O seletor de um slot restringe qual a Feature que o pode preencher, e a respetiva lista inject indica como o material da Feature pode ser entregue. Um slot obrigatório tem de estar vinculado em cada instância, por um acoplamento na instância ou num âmbito acima dela, e um slot sensível é declarado para tratar material secreto. Uma Feature também se pode acoplar com um nome que nenhum slot declara.

Nenhum slot de acoplamento declarado.

Lista de autorizações de autoinjeção

env

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é apresentada como uma aresta quebrada em vez de uma ligação.

Usa

Usado por

Referência do conceito Component →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design partilhado do Aggrega.

Privacidade