11 Commits

Author SHA1 Message Date
wangbin
57820b16a3 fix(api): refuse deleting a storage connection still referenced by workflows
handleStorageConnectionsDelete performed a hard DeleteOne with only a tenant
check, so a connection still referenced by a workflow node's connectionId could
be deleted — leaving a dangling reference that breaks workflow save/run
validation ("connectionId must reference an existing storage connection") with
no recovery path (the record is hard-deleted and unaudited). Add a reference
guard: before deleting, scan the connection's organization for workflows whose
nodes reference it; if any, return 409 Conflict listing the referencing
workflow/node ids so the caller can remove the reference first. Reuses the
existing ListAllWorkflowsByOrganization store method (no schema/interface change,
no runtime-path impact).

Co-Authored-By: Claude <noreply@anthropic.com>
2026-07-09 21:55:13 +08:00
eust-w
c577a44b7c 🐛 Dedupe WiLoR asset packages 2026-07-06 17:02:35 +08:00
eust-w
3ee2344fa5 🐛 Hydrate run artifacts for asset lists 2026-07-06 16:50:38 +08:00
eust-w
d56f3e5d9a ✨ Surface WiLoR outputs as data assets 2026-07-06 16:32:19 +08:00
eust-w
43a8efc74f 🛡️ Remove hardcoded BOS runtime endpoint 2026-06-17 14:14:35 +08:00
eust-w
406d77a025 🛡️ Validate source data sources 2026-06-17 06:46:51 +08:00
eust-w
520482645a 🛡️ Harden sampling rule percentages 2026-06-17 05:45:34 +08:00
eust-w
b1eb2104c2 🛡️ Harden data asset payload summaries 2026-06-17 05:34:06 +08:00
eust-w
71faac3160 🧭 Clarify derived data lineage 2026-06-16 18:45:48 +08:00
eust-w
2aa82f98ed ✨ Add GPU scheduling and API token hardening 2026-06-15 16:15:16 +08:00
eust-w
43326d6a5e feat(platform): land workflow, data tooling, and docs updates
Include the accumulated workflow scheduling, run history, subtree rerun, operator UI, deployment, data asset, object storage, database browser, and documentation changes currently in the worktree.
2026-04-24 12:29:46 +08:00