databases
Managed databases by name. Each environment gets its own instance (or a branch, for previews).
- Type: map of names to object
- Since: manifest v1
Example
Section titled “Example”databases: main: engine: postgres plan: standardEach entry
Section titled “Each entry”A managed database. Backed up by default to two off-site locations, with daily restore tests.
Fields
Section titled “Fields”| Field | Type | What it does |
|---|---|---|
engine * |
postgres, valkey, mysql |
Database engine. |
version |
string | Major version. |
plan |
starter, standard, ha, ha-plus |
starter one instance, 7-day PITR; standard 14-day PITR and daily restore tests; ha adds a synchronous replica with automatic failover and 30-day PITR; ha-plus adds read replicas and 35-day PITR. |
storage |
size | Storage size. |
backups |
object | Backup settings beyond the plan defaults. |
extensions |
list of pgvector, postgis, pg_trgm, pg_stat_statements, pgcrypto, uuid-ossp, citext, hstore, pg_partman, timescaledb, pg_cron |
Postgres extensions from the allowlist. |
maintenance_window |
string | Weekly window (UK time) for patching and maintenance. |
masking |
map of names to null or string | Masking rules applied to database branches before they are attached (mandatory for special-category projects). |
pooling |
boolean | Put a connection pooler in front (Postgres). |
public |
object | Public access through the TCP proxy. |
* required