Yassin Kortam 87c2e03af8 feat(db): opt-in REPLICA IDENTITY FULL after prisma migrations (#35267) ... Logical replication consumers need FULL replica identity to reconstruct the old row of an UPDATE or DELETE, and prisma leaves every table it creates at the postgres default. Operators had to re-apply the setting by hand after each migration run. Setting LITELLM_SET_REPLICA_IDENTITY_FULL now re-asserts it on every LiteLLM table at the end of a successful migration run, through the prisma CLI so the dependency-free proxy-extras package stays that way. Tables that are already FULL are skipped, foreign tables in the same schema are left alone, and a database that refuses the ALTER is reported rather than failing the run. Resolves LIT-3022		2026-07-30 15:45:40 -07:00
..
test_db_schema_migration.py	test(proxy): stop running real-DB tests in GitHub Actions unit jobs (#29700)	2026-06-04 14:56:02 -07:00
test_offline_image_migration.py	fix(docker): bake non_root prisma engines at /opt/prisma so migrations run offline for any uid (#34325)	2026-07-22 23:03:39 -07:00
test_replica_identity_full.py	feat(db): opt-in REPLICA IDENTITY FULL after prisma migrations (#35267)	2026-07-30 15:45:40 -07:00