83ed4f315b
- Stripe Connect: onboarding, balance, SellerDashboardView - Interceptors: auth.ts, error.ts extracted, facade - Grafana: dashboards enriched (p50, top endpoints, 4xx, WS, commerce) - E2E commerce: product->order->review->invoice - SMOKE_TEST_V0602, RETROSPECTIVE_V0602, PAYOUT_MANUAL - Archive V0_602 scope, V0_603 placeholder, SCOPE_CONTROL v0.603 - Fix sanitizer regex (Go no backreferences) - Marketplace test schema: product_licenses, product_images, orders, licenses
1.4 KiB
1.4 KiB
Database Migrations
Overview
Veza uses SQL migrations stored in veza-backend-api/migrations/. Migrations are applied in order by filename (lexicographic sort).
Migration Naming
- Format:
NNN_description.sql(e.g.101_product_reviews.sql) - Use snake_case for descriptions
- Down migrations (rollback):
NNN_description_down.sqlwhen needed
Squash Script
The scripts/squash_migrations.sh script generates a baseline SQL file that concatenates all migrations into a single file. This is useful for:
- Fresh database setup
- Creating a clean baseline for new environments
- Versioned releases (e.g.
baseline_v0601.sql)
Usage
# From project root
./scripts/squash_migrations.sh
Output: veza-backend-api/migrations/baseline_v0601.sql
Procedure
- Run the script after adding new migrations
- Update the version in the script (e.g.
baseline_v0601.sql) for each release - Update the migration range comment (e.g.
001-113) to reflect the latest migration number - The baseline file is auto-generated; do not edit it manually
Adding New Migrations
- Create a new file:
veza-backend-api/migrations/NNN_description.sql - Use the next available number (check existing migrations)
- Write idempotent SQL when possible (e.g.
IF NOT EXISTS) - Test locally before committing
- Run
squash_migrations.shto update the baseline for the release