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.
Provenance
- Content digest
- sha256:383ba4f751fe064be0c66c2ad2bc30ea2ff9b75171558aacde8cb5307b4c6d68
- Published
- 2026-11-10T10:10:44Z
- 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:a0e9576b7851a3aef4c001402e16ca8313944e17607b33ccb645975b2a17cdd4
Reference at this version
oci://hub.aggrega.ai/component/core/datastore/mariadb:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| database | string | — | yes | Logical database name created on startup. |
| user | string | — | no | Application-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. |
| charset | string | utf8mb4 | no | Default 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. |
| collation | string | utf8mb4_general_ci | no | Default 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_scripts | object | — | no | SQL scripts executed on first database initialization. Each key is a filename, each value is the SQL content. Scripts run in alphabetical key order. |
| custom_config | string | — | no | Raw server configuration block (my.cnf format). Injected verbatim into the server configuration file. |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 3306 | no | Server listen port. Most operators should omit this and let the Recipe assign the default (3306). |
| engine_version | string | 11.4 | no | Server binary version. |
| compute | object | — | no | — |
| storage | object | — | no | — |
| ha | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
| control_plane_present | boolean | false | no | Operator 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. |
| credentials | string (generated | supplied) | generated | no | Who 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_secret | string | no | Name 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. |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| host | string | — | yes | 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. |
| port | integer | — | yes | TCP port the server accepts connections on. It follows the port an operator set, so a consumer reads it rather than assuming 3306. |
| user | string | — | no | Name of the login role a consumer authenticates as. The matching password arrives through the credential attached to the component, never through this contract. |
| database | string | — | no | Name 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. |
| protocol | string | — | no | Wire protocol the published address speaks — `mariadb`, which is what a consumer selects a driver for. |
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.
No uses sockets declared.
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.
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| root_password | — | yes | — | yes | 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 | — | no | env, file | yes | 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. |
Self-inject allowlist
env, file
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
This entity uses nothing in the catalog.
Used by
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «checkpointer_db»
uses socket «checkpointer_db»
uses socket «backend»
uses socket «backend»
uses socket «backend»
uses socket «storage»
uses socket «metadata_store»
uses socket «target_datastore»
uses socket «backend»
uses socket «databases»
uses socket «etcd»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «forward_target»
uses socket «backend»
uses socket «cache»
uses socket «chunk_cache»
uses socket «scrape_target»
uses socket «backend»
uses socket «backend»
uses socket «database»
applies to
applies to
applies to
implements
implements
implements
implements
implements
implements
implements