Skip to content

feat: write to Postgres, and drop the migrations that never ran - #13

Merged
bludot merged 1 commit into
mainfrom
feat/postgres
Aug 22, 2026
Merged

bludot merged 1 commit into
mainfrom
feat/postgres

Conversation

@bludot

@bludot bludot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

This service consumes CDC events and writes into the shared database, which is now Postgres. Only the sink driver and DSN change — the writes already go through GORM, which is dialect-neutral, so no query in this repository needed rewriting.

The migrations are removed, not converted

They created tables anime-api creates, in the same database, tracked in the same schema_migrations table, with no DBMIGRATIONTABLE to separate them. Two services owning one schema is precisely the arrangement that already produced a collision between anime-api and news-ingest.

They were also dead:

  • event-chart has no migration job template — only deployment, configmap, hpa, service
  • every workload in it runs a serve-* command; none runs migrate

So migrate up has never run from this repository in production. The migrate cobra commands go with them, since nothing is left for them to do.

Config

DBPORT defaults to 5432, DBSSL to require, matching the five services already moved.

🤖 Generated with Claude Code

This service consumes CDC events and writes into the shared database, which is
now Postgres. Only the sink driver and DSN change; the writes already go through
GORM, which is dialect-neutral, so no query needed rewriting.

The migrations are removed rather than converted. They created tables anime-api
creates in the same database, tracked in the same schema_migrations table, so
two services owned one schema -- the arrangement that already caused a collision
between anime-api and news-ingest.

They were also dead: event-chart has no migration job template, and every
workload here runs a serve-* command, so `migrate up` has never run from this
repository in production. The migrate cobra commands go with them.

DBPORT now defaults to 5432 and DBSSL to require, matching the services already
moved.
@bludot
bludot merged commit 2a4981d into main Aug 22, 2026
2 checks passed
@bludot

bludot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

🎉 This PR is included in version 1.15.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant