Component
core/compute/worker
A generic background-worker primitive. Its operational type is `worker` — long-running, stateless compute that pulls from queues or runs background loops with zero inbound application ports — and it adds two optional integer fields, `queue_depth_hint` and `concurrency`, to the shared base schema's documentation knobs. An Aggregate declares this for a component that consumes work rather than accepting inbound application traffic, which is what `server` is for. Declaring no `provides`, it publishes nothing across an edge. On a Kubernetes cluster it is a Deployment. In an AWS account with an ECS cluster and a VPC, terraform/worker-ecs and cloudformation/worker-ecs run it as an Amazon ECS service on Fargate. In a Google Cloud project with a VPC network, terraform/worker-cloud-run runs it as a Cloud Run worker pool; in an Azure subscription with a Container Apps environment, terraform/worker-container-apps as a container app with no ingress. The catalog pins no image, so nothing renders until the Release sets `infra.image`. The image is the Release's own code, so an edge from this component delivers what its `inject:` block dictates: `env` entries become variables everywhere, beside both values' default names, which the component's own `env` entries may replace and, while each is the default, no edge may dictate; `file` entries files on Kubernetes and Container Apps alone; 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 rendered in the clear on every realization; no realization delivers `core/referenced-secret` or `core/random-password` to it, and the helm realization refuses either by name.
Procedencia
- Digest del contenido
- sha256:eaf961fd361445f4512b58fad46e497d53ac752d243406b9395ec8b3c8110bb3
- Publicado
- 2026-11-10T10:10:20Z
- 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:13aedbc915f892c29dda59a0edb42204121785a99b8bcf9817edaeef5420153b
Referencia en esta versión
oci://hub.aggrega.ai/component/core/compute/worker:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
Extiende BaseComponents#/schemas/BaseComponentParameter
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| queue_depth_hint | integer (min 0) | — | no | — |
| concurrency | integer (min 1) | — | no | — |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| image | string | — | no | Container image running the worker loop. |
| replicas | integer (min 1) | 1 | no | Replica count, the number of tasks on Amazon ECS, of instances in a Cloud Run worker pool and of replicas on Container Apps, up to 300 there. Each replica pulls its own work, so raising it widens throughput rather than sharing one queue position. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-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 service runs under, each under its target's own spelling (subnet_ids on terraform, Subnets on CloudFormation), the Cloud Run realization the project, region, VPC network and service account the worker pool runs in, the Container Apps realization the environment and resource group the app runs in and the identities and registry it pulls with, and the Kubernetes realization reads 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
- $refextiende el esquema (values)
BaseComponents#/schemas/BaseComponentParameter
Usado por
usa el socket «scrape_target»
se aplica a
se aplica a
se aplica a
implementa
implementa
implementa
implementa
implementa