chore(db): retire the four per-service databases (ADR-0030 Phase 4)#262
Merged
Conversation
The techgarden monolith is live and validated, so the iris/dopamenu/plates/ notifications databases, their managed app roles, and their per-service ExternalSecrets are removed from the shared postgresql cluster. Only techgarden_app + techgarden-database remain. reclaim=retain, and cnpg does not drop an unmanaged role, so this change drops NO data — the DBs/roles persist until dropped by hand. iris's Bitwarden entry (6389718c) is KEPT: it was promoted to back techgarden_app and the live api. Only dopamenu/plates/notifications had their own entries (deleted separately in Bitwarden). Follow-up (manual, after soak): DROP DATABASE + DROP ROLE for the four, then delete the three orphaned Bitwarden entries.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 4 of the ADR-0030 backend consolidation. The
techgardenmodular monolith is live in dev and validated (techgarden PR #112, deployed + Phase-3 green 2026-07-17), so the four old per-service databases are retired from the sharedpostgresqlcluster.What this removes
iris-database,dopamenu-database,plates-database,notifications-database(databases.yaml)iris_app,dopamenu_app,plates_app,notifications_app(cluster.yaml){iris,dopamenu,plates,notifications}-db-app-credentials(app-externalsecrets.yaml)techgarden-database+techgarden_app+techgarden-db-app-credentialsare untouched.This drops NO data
Every Database CR is
databaseReclaimPolicy: retain, and cnpg never drops a role it stops managing. So merging this leaves the four DBs and roles intact but unmanaged — a safe soak window. Reverting this PR fully restores management. The actualDROP DATABASE/DROP ROLEis a separate manual step run by hand after soak.Bitwarden
6389718c…is KEPT — it wasiris_app's entry, promoted in PR1 to backtechgarden_app(referenced by the liveapideployment +techgarden-db-app-credentials). Removing theiris-db-app-credentialsk8s ExternalSecret is safe; the Bitwarden entry stays.14eb7f8b(dopamenu),e333d7be(plates),7015df9c(notifications).Manual follow-up (after soak, by hand)
Full runbook:
projects/api/deploy/phase-4-teardown.mdin the techgarden repo (PR #113).🤖 Generated with Claude Code