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

Component

core/datastore/mariadb

A MariaDB relational database. Provider-agnostic: the same component is implemented by Helm Recipes (Workload synthesis to native Kubernetes resources), Terraform Recipes (AWS RDS), CloudFormation Recipes, Compose Recipes (local development), and a controller-driven Helm Recipe that emits a MariaDB custom resource for the mariadb-operator control plane to reconcile. Reach for the synthesis Recipe on a cluster that runs no MariaDB control plane — it needs no controller installed and no chart repository, so it builds with nothing fetched — and for the controller-driven Recipe where the control plane is already in place and the cluster should own upgrades, rolling restarts, credential rotation and, through infra.ha, replication and failover. On AWS RDS through Terraform, reach for terraform/mariadb-rds-terraform-aws-modules, which vendors the terraform-aws-modules project's published RDS module, where the pull may fetch it from its git repository; reach for terraform/mariadb-rds, which authors its own body, or terraform/mariadb-rds-module, which vendors a module kept beside it, where nothing may be fetched, and for terraform/mariadb-rds where read replicas are needed. Backup is the core/backup attachment, written in the Release. The managed Recipes configure the service's own automated backups from it, bound to terraform/backup-native or cloudformation/backup-native, and keep them for 7 days with none attached. The controller-driven Recipe is backed up through helm/backup-mariadb-operator, the synthesized one by the backup product the Manifest binds; the Compose Recipe has none, so an attachment halts there.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:383ba4f751fe064be0c66c2ad2bc30ea2ff9b75171558aacde8cb5307b4c6d68
Publicado
2026-11-10T10:10:44Z
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:a0e9576b7851a3aef4c001402e16ca8313944e17607b33ccb645975b2a17cdd4

Referencia en esta versión

oci://hub.aggrega.ai/component/core/datastore/mariadb:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
databasestring—síLogical database name created on startup.
userstring—noApplication-level database user (non-root). Omit for root-only access. RDS creates only its master user, admin, which the managed Recipes publish as provides.user, so each of them halts the build when this is set.
charsetstringutf8mb4noDefault character set. terraform/mariadb-rds-terraform-aws-modules sets it in the parameter group it creates; the other managed Recipes do not read it, and the instance takes its parameter group's.
collationstringutf8mb4_general_cinoDefault collation. terraform/mariadb-rds-terraform-aws-modules sets it in the parameter group it creates; the other managed Recipes do not read it, and the instance takes its parameter group's.
init_scriptsobject—noSQL scripts executed on first database initialization. Each key is a filename, each value is the SQL content. Scripts run in alphabetical key order.
custom_configstring—noRaw server configuration block (my.cnf format). Injected verbatim into the server configuration file.

Dimensionamiento del operador

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

NombreTipoPredeterminadoObligatorioDescripción
portinteger (min 1024, max 65535)3306noServer listen port. Most operators should omit this and let the Recipe assign the default (3306).
engine_versionstring11.4noServer binary version.
computeobject—no—
storageobject—no—
haobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.
control_plane_presentbooleanfalsenoOperator affirmation that the mariadb-operator control plane is installed in the target cluster. A controller-driven realization halts the build unless this is set true, so a MariaDB custom resource is never emitted as an orphan into a cluster that cannot reconcile it. Every other realization ignores this flag.
credentialsstring (generated | supplied)generatednoWho owns the database's credentials on a controller-driven realization. `generated` — the controller creates the credential Secrets and owns both the root password and the application user's, which is what it does when nothing is supplied; the developer's `database` and `user` values are still honored, and no password reaches the rendered artifact. `supplied` — the controller reads both passwords from an existing Secret named in `credentials_secret` and generates neither. Every other realization halts the build on `supplied`: the synthesized ones take the root password from the `root_password` credential slot and the application user's from `user_password`, and on the managed ones RDS owns the password.
credentials_secretstringnoName of the existing Secret a controller-driven realization reads the database credentials from when `credentials` is `supplied`. The Secret lives in the same namespace as the database and carries two entries: `root-password` for the root account and `password` for the application user. Leave it empty when `credentials` is `generated`; a controller-driven build halts if `supplied` is selected without it. Every other realization reads no Secret by this name and halts the build when it is set.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—síAddress a client opens its database connection to. On the in-cluster realizations it is the Service's DNS name; on a managed one it is a pointer string the provisioning tool resolves to the instance's address once the infrastructure has been applied, or the DNS name the Release sets in infra.overrides.host, so a consumer on another target receives an address it can resolve.
portinteger—síTCP port the server accepts connections on. It follows the port an operator set, so a consumer reads it rather than assuming 3306.
userstring—noName of the login role a consumer authenticates as. The matching password arrives through the credential attached to the component, never through this contract.
databasestring—noName of the logical database created at startup. A consumer names it in its connection string to land in the right database rather than the server's default.
protocolstring—noWire protocol the published address speaks — `mariadb`, which is what a consumer selects a driver for.

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.

No se declararon sockets uses.

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.

SlotSelectorObligatorioInyecciónSensibleDescripción
root_password—sí—síRoot database password. Recipe controls delivery (Black-Box). On helm/mariadb-cluster with infra.credentials generated the controller generates it, so the slot is bound with core/generated-secret, mapped to helm/generated-secret. On the RDS Recipes RDS generates the password of the master user, admin, and keeps it in AWS Secrets Manager, so the slot takes core/generated-secret there, and any other credential halts the build.
user_password—noenv, filesíApplication user password. Unattached, helm/mariadb sets it to the development literal `apppass`, which this catalog publishes, so every Release built with that Recipe that leaves the slot unattached shares that password; on helm/mariadb-cluster with infra.credentials generated the controller generates it. The RDS Recipes create only the master user, admin, and halt the build when this slot is filled.

Lista de permitidos de autoinyección

env, file

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

Esta entidad no usa nada del catálogo.

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