Component
core/ai-agent/agenta-migrations
The schema-migration step of an agent workspace — the run that creates and updates the platform's tables. It applies the migration history the platform ships to both of its databases: the one holding the platform's own model, and the one holding traces. It runs to completion and exits, which is what makes it a different operational shape from every other tier of this platform. It reaches the relational backend through the `backend` socket, using the two database names given on that edge, and it declares nothing else: the run reads no cache, takes no queue work, writes no files, and authenticates no user, so giving it a cache, queue, object-store or authentication socket would be declaring a dependency it does not have. Wire this in because the platform's services do not create their own tables. Without this run the databases stay empty and every service starts, connects, and then fails on its first query — a failure that reads as a broken installation rather than as a missing step, which is why the step is a declared component rather than something a reader is expected to remember. It serves no port and nothing connects to it, so it publishes no provides contract. Because it exits, an Aggregate sequences it ahead of the services that need the schema; it is written to be safe to run again, so re-running it on an already-migrated database applies nothing and succeeds. Realized on Kubernetes via its Helm Recipe, which synthesizes the step as a run-to-completion workload rather than a Deployment, running the platform image under its migration entry point.
来源
- 内容摘要
- sha256:9450af80a213a43551864c97867f66589819d956a4bac6391d19d7f2cb86fab7
- 发布时间
- 2026-11-10T10:07:17Z
- 签名身份
- 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:8dd056cd777a5f7b2e7c157ceee295143ad361e8ead33cca8e3fa7c7cd843c78
此版本的引用
oci://hub.aggrega.ai/component/core/ai-agent/agenta-migrations:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| apply_on_start | boolean | true | 否 | Apply any migration the databases are behind on. Turned off, the run reports what it would apply and changes nothing, which is how an installation that migrates its databases by another route keeps this step in place without it acting. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| engine_version | string | v0.114.1 | 否 | Platform API container image tag. The migration history is shipped inside this image, so it is the same tag the services run and a Release moves them together. |
| log_level | string (DEBUG | INFO | WARNING | ERROR | CRITICAL) | INFO | 否 | Log verbosity the run 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 run 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. |
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
未声明附加槽位。
自注入允许列表
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 →
被使用
使用套接字 «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»
适用于
适用于
实现