stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

stela ops usage fixes roles propagation and timoeut, one account to support multi tenants, migrations consolidation, search to support documentation, doctor and open api vector db search

Browse Source
This commit is contained in:
master
2026-02-22 19:27:54 +02:00
parent a29f438f53
commit bd8fee6ed8
373 changed files with 832097 additions and 3369 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
docs/operations/upgrade-runbook.md
View File

@@ -122,26 +122,37 @@ kubectl get pods -n stellaops-green -w
### Run Migrations
```bash
# Step 16: Apply Category A migrations (startup)
# Step 16: Check current migration state (CLI-registered modules)
stella system migrations-status --module all
# Step 17: Verify checksums before execution
stella system migrations-verify --module all
# Step 18: Preview release migrations (manual gate)
stella system migrations-run \
--category A \
--namespace stellaops-green
--module all \
--category release \
--dry-run
# Step 17: Verify migration success
stella system migrations-status --namespace stellaops-green
# All migrations should show "Applied"
# Step 18: Apply Category B migrations if needed (manual)
# Review migration list first
stella system migrations-pending --category B
# Apply after review
# Step 19: Execute approved release migrations
stella system migrations-run \
--category B \
--namespace stellaops-green \
--confirm
--module all \
--category release \
--force
# Step 20: Verify migration success
stella system migrations-status --module all
```
Migration notes:
- Category names are `startup`, `release`, `seed`, and `data`.
- Compose and service startup paths may apply additional migrations outside CLI coverage.
- Use `docs/db/MIGRATION_INVENTORY.md` for current module-by-module runner coverage before production upgrade.
- Canonical consolidation policy and wave plan are in `docs/db/MIGRATION_CONSOLIDATION_PLAN.md`.
- For upgradeable on-prem environments, treat this CLI sequence as the required release migration gate.
- UI-triggered migration operations must execute through Platform admin APIs (`/api/v1/admin/migrations/*`) with `platform.setup.admin` (no browser-direct PostgreSQL access).
### Evidence Migration (If Required)
```bash