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

Component

core/compute/task

A generic ephemeral compute primitive. Its operational type is `task` — ephemeral compute that runs to completion and dies, such as a database migration — with two optional fields of its own, `schedule` and `timeout`. An Aggregate declares this for work that ends, rather than `server` or `worker`, which are both long-running. helm/task runs it on Kubernetes, on its `schedule` as a CronJob and once at deploy without one. compose/task runs it on Docker Compose once at each `docker compose up`, and refuses a `schedule`. terraform/task-ecs and cloudformation/task-ecs run it as an Amazon ECS task on Fargate, on its schedule through EventBridge Scheduler, and refuse it with none, as nothing on AWS would start it. With no `schedule`, `core/manual-trigger` holds it until someone starts a run, with the command each realization's description names. Nothing renders until the Release sets `infra.image`. The image is the Release's own code, so an edge delivers what its `inject:` block dictates, and no declared socket narrows the mechanism: `env` entries become variables beside `TASK_TIMEOUT`, `timeout`'s default name, which the component's own `env` entries may replace and, while it is the default, no edge may dictate; `file` entries files, read-only on Kubernetes, and none on Amazon ECS; and `arg` or any other mechanism is refused by name, as no realization renders a command line. A `core/secret-value` attachment's value is written into the rendered workload in the clear; no realization delivers `core/referenced-secret` or `core/random-password` to it, and the helm realization refuses either by name.

Versión

1.0.01.0.1

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:dbcdf6051b686ddd8192ca016c4c9d0d1fa9eca3bc6f5f2d970e2cf9acf01afa
Publicado
2026-11-10T10:10:18Z
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:4bc801a725e11fd739d1d227b8f19c81a12c696cd20e65cc3500cc2b83d0b7d0

Referencia en esta versión

oci://hub.aggrega.ai/component/core/compute/task:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

Extiende BaseComponents#/schemas/BaseComponentParameter

NombreTipoPredeterminadoObligatorioDescripción
schedulestring—noA cron expression of five fields — minute, hour, day of the month, month and day of the week — such as 30 2 * * 1-5. Kubernetes runs it in its controller manager's time zone; Amazon ECS runs it through EventBridge Scheduler, in UTC unless the Release names a time zone, and refuses one the scheduler cannot carry exactly, such as one restricting both the day of the month and the day of the week. Docker Compose has no scheduler and refuses a schedule.
timeoutstring—noHow long a run may take, delivered to the container as TASK_TIMEOUT, or under the name an env entry of the component's own inject block reading it alone gives it, for the application's own code to honour: no realization sets a deadline at which the platform stops a run.

Dimensionamiento del operador

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

NombreTipoPredeterminadoObligatorioDescripción
imagestring—noContainer image the run executes.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads: the Amazon ECS realizations read the cluster, subnets, security groups and roles the task runs and is started under, and the schedule's time zone, each under its target's own spelling (subnet_ids on terraform, Subnets on CloudFormation), and the Kubernetes and Docker Compose realizations read none of its keys.

Contrato de salida

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

No se declararon valores de salida.

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.

No se declararon sockets uses.

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