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, and on Docker Compose so is a `core/referenced-secret` attachment's origin; no other realization delivers `core/referenced-secret`, none delivers `core/random-password`, and the helm realization refuses either by name.
版本
来源
- 内容摘要
- sha256:03cf624d2ae77e9ac8b0ad1c9a2a15ef81253d582ce2d53758e2a0ea5632afa3
- 发布时间
- 2026-11-15T08:09:01Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/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:2a329698f512d71016a645fb928c74351d20be091ac3ac5cdb035a33021f9dff
此版本的引用
oci://hub.aggrega.ai/component/core/compute/task:1.0.1开发者参数
开发者在 Aggregate 中设置的值。
扩展 BaseComponents#/schemas/BaseComponentParameter
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| schedule | string | — | 否 | A 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. |
| timeout | string | — | 否 | How 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. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| image | string | — | 否 | Container image the run executes. |
| compute | object | — | 否 | — |
| overrides | object (open) | — | 否 | 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 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. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
未声明输出值。
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
未声明 uses 套接字。
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
未声明附加槽位。
自注入允许列表
env
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- $ref扩展模式(values)
BaseComponents#/schemas/BaseComponentParameter
被使用
适用于
适用于
实现
实现
实现
实现