Component
core/ai-agent/agenta-cron
The scheduler of an agent workspace — the process that decides when a time-triggered thing is due and puts it on the queue. A background agent set to run every morning, and the platform's own periodic housekeeping, both become work because this tier woke up and enqueued them. It is a resident process carrying its own schedule table rather than a platform-level scheduled object, which is how the platform's own published manifests run it: one container that stays up and fires on its own clock. It reads the schedules from the relational backend wired through `backend`, using the two database names given on that edge, enqueues onto the queue wired through `queue`, and uses the cache wired through `cache` for the same read-caching the rest of the platform does. It performs none of the work itself — the queue-consuming worker tier does — so this tier stays small however much is scheduled. Wire here because a schedule with nothing evaluating it never fires. That failure is silent from every other tier: the agent exists, its schedule is stored, and nothing happens at the appointed time. Exactly one instance of this component belongs in an Aggregate. It is not horizontally scalable — two schedulers reading one schedule table each enqueue the same due item — so scale is a question for the worker tier rather than this one. It serves no port and nothing connects to it, so it publishes no provides contract. Realized on Kubernetes via its Helm Recipe, which synthesizes the tier as a stateless single-replica Deployment with no Service, running the platform image under its scheduler entry point.
来源
- 内容摘要
- sha256:6dcf410ace725868711c9c9f4bb802658e0fec5c9564356e57fdc3b72b67cfad
- 发布时间
- 2026-11-10T10:07:15Z
- 签名身份
- 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:2bc777c70c7ad3d90fa5f962945cc8e406c0c7796f916a6372dc575d68cbe520
此版本的引用
oci://hub.aggrega.ai/component/core/ai-agent/agenta-cron:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
未声明开发者参数。
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| engine_version | string | v0.114.1 | 否 | Platform API container image tag. This tier runs the same image as the control-plane API under a different entry point, so a Release moves both together. |
| log_level | string (DEBUG | INFO | WARNING | ERROR | CRITICAL) | INFO | 否 | Log verbosity the scheduler emits. |
| compute | object | — | 否 | — |
| overrides | object (open) | — | 否 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
未声明输出值。
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
backend
- 选择器
- component.aggrega.ai/category=datastore
- 注入
- env
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | 否 | env | 是 | Password the scheduler authenticates to the relational backend this connection reaches with, delivered as an env secret reference and substituted into the connection URL at run time. The same credential is attached to the control-plane API's backend connection, because both reach the same server. Unattached, the Recipe emits the development literal `apppass`, the default the standard-library relational Recipes leave in place; this catalog publishes it, so every Release that leaves the slot unattached shares that password. |
cache
- 选择器
- component.aggrega.ai/category=datastore
- 注入
- env
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | 否 | file | 是 | Optional authority the platform's Redis client checks the cache's certificate against while the cache publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and names the file in the connection's URL. The build halts on a server_ca publishing no Secret name, and on one wired to a cache served without TLS. Fill it with core/referenced-secret. |
queue
- 选择器
- component.aggrega.ai/category=datastore
- 注入
- env
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | 否 | file | 是 | Optional authority the platform's Redis client checks the queue's certificate against while the queue publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and names the file in the connection's URL. The build halts on a server_ca publishing no Secret name, and on one wired to a queue served without TLS. Fill it with core/referenced-secret. |
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| auth_key | feature.aggrega.ai/kind=secret | 是 | env | 是 | Required key the platform signs its own internal tokens with. It carries the same value as the control-plane API's slot. There is no default: the build halts when nothing fills this slot. |
| crypt_key | feature.aggrega.ai/kind=secret | 是 | env | 是 | Required key stored credentials are encrypted under. It carries the same value as the control-plane API's slot. There is no default: the build halts when nothing fills this slot. |
自注入允许列表
env
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- 使用使用套接字 «backend»
component.aggrega.ai/category=datastore
附加槽位:credential
core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 → - 使用使用套接字 «cache»
component.aggrega.ai/category=datastore
附加槽位:server_ca
core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 → - 使用使用套接字 «queue»
component.aggrega.ai/category=datastore
附加槽位:server_ca
core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 →
被使用
使用套接字 «runner»
使用套接字 «api»
使用套接字 «runner»
使用套接字 «api»
使用套接字 «services»
使用套接字 «api»
使用套接字 «services»
使用套接字 «services»
使用套接字 «sandbox»
使用套接字 «plugin_daemon»
使用套接字 «ssrf_proxy»
使用套接字 «sandbox»
使用套接字 «plugin_daemon»
使用套接字 «ssrf_proxy»
使用套接字 «api»
使用套接字 «ssrf_proxy»
使用套接字 «api»
使用套接字 «api»
使用套接字 «sandbox»
使用套接字 «plugin_daemon»
使用套接字 «ssrf_proxy»
使用套接字 «sandbox»
使用套接字 «plugin_daemon»
使用套接字 «ssrf_proxy»
使用套接字 «target_agent»
使用套接字 «scrape_target»
适用于
适用于
适用于
实现