feat: Add database migration steps to CI and deployment workflows

- Add migration execution step in CI workflow before linter runs
- Configure DATABASE_URL environment variable for test database connection
- Add placeholder migration steps in deploy workflow for staging and production environments
- Include commented kubectl exec commands for future implementation in Kubernetes deployments
This commit is contained in:
nutcas3
2026-04-29 02:52:51 +03:00
parent 3cfd5d672c
commit 6fd5d89671
2 changed files with 18 additions and 0 deletions
+6
View File
@@ -40,6 +40,12 @@ jobs:
working-directory: apps/api-server
run: go mod download
- name: Run database migrations
working-directory: apps/api-server
env:
DATABASE_URL: postgresql://test_user:test_password@localhost:5432/test_db?sslmode=disable
run: go run cmd/migrate/main.go --action=up
- name: Run linter
working-directory: apps/api-server
run: |
+12
View File
@@ -170,6 +170,12 @@ jobs:
with:
version: 'latest'
- name: Run database migrations
run: |
echo "Running database migrations for staging..."
# kubectl exec -it deployment/api-server -- go run cmd/migrate/main.go --action=up
echo "Staging migrations complete"
- name: Deploy to staging cluster
run: |
echo "Deploying to staging..."
@@ -191,6 +197,12 @@ jobs:
with:
version: 'latest'
- name: Run database migrations
run: |
echo "Running database migrations for production..."
# kubectl exec -it deployment/api-server -- go run cmd/migrate/main.go --action=up
echo "Production migrations complete"
- name: Deploy to production cluster
run: |
echo "Deploying to production..."