Esta página se tradujo automáticamente. Leer el original en inglés.

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.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:9450af80a213a43551864c97867f66589819d956a4bac6391d19d7f2cb86fab7
Publicado
2026-11-10T10:07:17Z
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:8dd056cd777a5f7b2e7c157ceee295143ad361e8ead33cca8e3fa7c7cd843c78

Referencia en esta versión

oci://hub.aggrega.ai/component/core/ai-agent/agenta-migrations:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
apply_on_startbooleantruenoApply 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.

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
engine_versionstringv0.114.1noPlatform 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_levelstring (DEBUG | INFO | WARNING | ERROR | CRITICAL)INFOnoLog verbosity the run emits.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

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.

backend

Selector
component.aggrega.ai/category=datastore
Inyección
env

Slots que cada conexión a través de este socket puede llenar

SlotSelectorObligatorioInyecciónSensibleDescripción
credentialfeature.aggrega.ai/kind=secretnoenvsí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.

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

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad