Yassin Kortam 72c8888563 fix(docker): bake prisma offline in the componentized migrations image (#35485) ... The migrations image ran `prisma migrate deploy` against a bake anchored in $HOME with no node in the runtime stage, so prisma-client-py fell through to nodeenv and tried to download a Node runtime on first start. In an egress-restricted cluster that fails outright, and under an arbitrary uid the uid-specific cache path is unreadable, so the job never applies a migration. Move the bake to /opt/prisma with world-readable modes, install node in the runtime stage, and pin PRISMA_BINARY_CACHE_DIR / PRISMA_CLI_PATH / PRISMA_OFFLINE_MODE so the migration entrypoint runs the cached CLI directly. This is the same treatment the root, non_root and database images already carry. Resolves LIT-4727		2026-08-01 14:12:31 -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 prisma offline in the componentized migrations image (#35485)	2026-08-01 14:12:31 -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