Managed Databases

Verfügbarkeit

Managed Postgres ist noch nicht verfügbar. Current database service ist control-plane preview: validates requests, records metadata, generates one-time credential shape, kann DATABASE_URL publish, returns aber non-routable host stub-shared-pg-01.local. Es erstellt keinen database server, tenant, schema, backup oder recovery point.

Connect application nicht to record whose status stub ist. Treat successful API response nicht als proof dass storage exists.

Was Sie heute testen können

Preview useful für testing integration gegen planned contract:

app ownership checked by MCP wrapper;
database records können created und listed werden;
generated password returned nicht by later metadata reads;
DATABASE_URL kann handed to app-environment producer when producer token configured; und
app records returned database reference.

Publishing placeholder URL macht es nicht usable. Remove from app environment before real deployment.

MCP tools

Tool	Current behavior
`add_app_database(app_id, engine='postgres')`	Creates `stub` record. May publish placeholder `DATABASE_URL`.
`list_app_databases(app_id)`	Returns metadata only. Never returns password.

Returned status before anything else prüfen:


add_app_database(app_id='app-12345678', engine='postgres')


{
  "db_id": "db-a1b2c3d4e5f6",
  "engine": "postgres",
  "status": "stub",
  "env_published": false,
  "publish_skipped_reason": "OPENFACTORY_DB_PRODUCER_TOKEN is not configured"
}

Exact response kann auch one-time connection fields enthalten. In preview zeigen sie auf stub host und must not used as credentials für real workload.

REST contract

Platform-side routes:

Method	Path	Result
`POST`	`/api/app-infra/databases`	Creates preview record und returns one-time connection-shaped data.
`GET`	`/api/app-infra/databases/{db_id}`	Returns metadata without password.
`GET`	`/api/app-infra/databases?app_id={app_id}`	Lists metadata, optionally filtered by app.

Lower-level routes primarily für internal integration. Prefer owner-scoped MCP tool unless developing platform itself.

Before managed Postgres ready genannt werden kann

Production-capable release braucht evidence für all of following:

reachable Postgres service und real tenant provisioning;
network isolation between apps;
credential rotation und deprovisioning;
backup restore drills mit measured recovery results;
resource limits, monitoring und failure alerts; und
end-to-end application test writing data, redeploying und reading back.

Until checks pass in target environment, bring your own database und place real connection string in App environment variables.