Flows and dashboards are created by POST under an issued or superuser-pinned id; PUT only updates; deleted flows leave a tombstone with their key; the controller stores by id and runs by key, hooks live under /hooks/<flow id>; a key with state or queued work behind it is refused until cleared

This commit is contained in:
2026-11-02 17:41:23 +01:00
parent fae85f5ecb
commit 08a6376836
63 changed files with 2832 additions and 936 deletions
@@ -0,0 +1,35 @@
"""flow_tombstone
The last key of a deleted flow, so its history still reads as something.
Revision ID: c4f1a8e2d7b3
Revises: b9e4d2a7c1f6
Create Date: 2026-11-02
"""
import sqlalchemy as sa
import sqlmodel.sql.sqltypes
from alembic import op
# revision identifiers, used by Alembic.
revision = "c4f1a8e2d7b3"
down_revision = "b9e4d2a7c1f6"
branch_labels = None
depends_on = None
def upgrade():
op.create_table(
"flow_tombstone",
sa.Column("id", sqlmodel.sql.sqltypes.AutoString(length=255), nullable=False),
sa.Column(
"name", sqlmodel.sql.sqltypes.AutoString(length=255), nullable=False
),
sa.Column("deleted_at", sa.DateTime(timezone=True), nullable=False),
sa.PrimaryKeyConstraint("id"),
)
def downgrade():
op.drop_table("flow_tombstone")