stack.basicstack.de/apps/stalwart/stalwart-bootstrap-config.yaml

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: stalwart-bootstrap-config
  namespace: stalwart
data:
  # DEV-476: Bootstrap now points at the PostgreSQL config/data store.
  # PGPASSWORD is injected into the stalwart container from
  # secret/stalwart-postgres-credentials (see stalwart-fresh-deployment.yaml).
  config.json: '{"@type":"PostgreSql","host":"stalwart-postgres","port":5432,"database":"stalwart","authUsername":"stalwart","authSecret":{"@type":"EnvironmentVariable","variableName":"PGPASSWORD"},"useTls":false}'
Restore Stalwart bootstrap ConfigMap (non-destructive recovery) CONTEXT: DEV-403 - Stalwart pod not starting after ConfigMap revert ROOT CAUSE: - The stalwart-bootstrap-config ConfigMap was manually created on July 5 - It was added to GitOps at commit 191614f (12:27 today) - It was reverted at commit fcc5042 (12:56 today) - ArgoCD pruned the ConfigMap from the cluster after the revert - Stalwart deployment requires this ConfigMap to start RECOVERY: This commit restores the ConfigMap to Git so ArgoCD can recreate it. The ConfigMap content is identical to the working version from before. This is a non-destructive recovery - no data or accounts are affected. The actual Stalwart data on PVC stalwart-data remains intact. Co-Authored-By: Paperclip <noreply@paperclip.ing> 2026-07-26 13:09:20 +00:00			`---`
			`apiVersion: v1`
			`kind: ConfigMap`
			`metadata:`
			`name: stalwart-bootstrap-config`
			`namespace: stalwart`
			`data:`
feat(stalwart): switch config/data store from RocksDB to PostgreSQL (DEV-476) Following the DEV-473 rocksdb-to-postgres migration, point Stalwart's bootstrap config at the PostgreSQL store and expose PGPASSWORD to the container so the `authSecret: EnvironmentVariable` lookup resolves. - stalwart-bootstrap-config.yaml: config.json switches @type RocksDb -> PostgreSql (host=stalwart-postgres, db=stalwart, authUsername=stalwart, authSecret=EnvironmentVariable/PGPASSWORD, useTls=false). - stalwart-fresh-deployment.yaml: adds PGPASSWORD env from secret/stalwart-postgres-credentials.POSTGRES_PASSWORD on the stalwart container. - stalwart-config.yaml: mirrors the switch in stalwart.toml as documentation (the running pod uses `--config /etc/stalwart/config.json`, not the toml). Board (DEV-476) explicitly asked for the manifest-level switch after the web UI save failed with a `Permission denied` on the read-only bootstrap emptyDir. Co-Authored-By: Paperclip <noreply@paperclip.ing> 2026-08-15 14:46:29 +00:00			`# DEV-476: Bootstrap now points at the PostgreSQL config/data store.`
			`# PGPASSWORD is injected into the stalwart container from`
			`# secret/stalwart-postgres-credentials (see stalwart-fresh-deployment.yaml).`
			`config.json: '{"@type":"PostgreSql","host":"stalwart-postgres","port":5432,"database":"stalwart","authUsername":"stalwart","authSecret":{"@type":"EnvironmentVariable","variableName":"PGPASSWORD"},"useTls":false}'`