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:
@@ -607,6 +607,25 @@ class AlertSent(SQLModel, table=True):
|
||||
ts: float = Field(index=True)
|
||||
|
||||
|
||||
# -----------------------------------------------------------------------------
|
||||
# Flow tombstones
|
||||
#
|
||||
# A deleted flow's runs, events and metrics stay, filed under its id. New ids
|
||||
# are opaque, so without the key the flow last had they would name nothing
|
||||
# anyone recognises.
|
||||
# -----------------------------------------------------------------------------
|
||||
|
||||
|
||||
class FlowTombstone(SQLModel, table=True):
|
||||
"""A deleted flow's last key, kept while history names its id."""
|
||||
|
||||
__tablename__ = "flow_tombstone"
|
||||
|
||||
id: str = Field(primary_key=True, max_length=255)
|
||||
name: str = Field(max_length=255)
|
||||
deleted_at: datetime = Field(default_factory=get_datetime_utc, sa_type=UTCDateTime)
|
||||
|
||||
|
||||
# -----------------------------------------------------------------------------
|
||||
# Worker tokens
|
||||
#
|
||||
|
||||
Reference in New Issue
Block a user