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.
Provenance
- Content digest
- sha256:9450af80a213a43551864c97867f66589819d956a4bac6391d19d7f2cb86fab7
- Published
- 2026-11-10T10:07:17Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/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
Reference at this version
oci://hub.aggrega.ai/component/core/ai-agent/agenta-migrations:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| apply_on_start | boolean | true | no | 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. |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| engine_version | string | v0.114.1 | no | 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 | no | Log verbosity the run emits. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Output contract
Values this component publishes to consumers over the uses topology.
No output values declared.
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
backend
- Selector
- component.aggrega.ai/category=datastore
- Inject
- env
Slots each connection through this socket may fill
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | no | env | yes | 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. |
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
No attachment slots declared.
Self-inject allowlist
env
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
- usesuses socket «backend»
component.aggrega.ai/category=datastore
Attachment slots: 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 →
Used by
uses socket «runner»
uses socket «api»
uses socket «runner»
uses socket «api»
uses socket «services»
uses socket «api»
uses socket «services»
uses socket «services»
uses socket «sandbox»
uses socket «plugin_daemon»
uses socket «ssrf_proxy»
uses socket «sandbox»
uses socket «plugin_daemon»
uses socket «ssrf_proxy»
uses socket «api»
uses socket «ssrf_proxy»
uses socket «api»
uses socket «api»
uses socket «sandbox»
uses socket «plugin_daemon»
uses socket «ssrf_proxy»
uses socket «sandbox»
uses socket «plugin_daemon»
uses socket «ssrf_proxy»
uses socket «target_agent»
applies to
applies to
implements