Fix alembic migration fork: chain 002_cameras after 002_fires
Some checks failed
build-and-deploy / build (push) Failing after 4s

002_fires and 002_cameras both had down_revision=001_initial, producing two
heads so 'alembic upgrade head' fails at container startup and the dashboard
never boots. Tables are independent; linearize 001 -> 002_fires -> 002_cameras.
This commit is contained in:
Sirius DevOps 2026-08-24 15:44:05 -04:00
parent cf98af8101
commit 172273bed6

View file

@ -1,7 +1,7 @@
"""cameras table for open-camera discovery """cameras table for open-camera discovery
Revision ID: 002_cameras Revision ID: 002_cameras
Revises: 001_initial Revises: 002_fires
Create Date: 2026-08-24 Create Date: 2026-08-24
""" """
@ -10,7 +10,7 @@ import sqlalchemy as sa
from sqlalchemy.dialects.postgresql import UUID from sqlalchemy.dialects.postgresql import UUID
revision = '002_cameras' revision = '002_cameras'
down_revision = '001_initial' down_revision = '002_fires'
branch_labels = None branch_labels = None
depends_on = None depends_on = None