Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
819 Commits 1 Branch 8 Tags
b7f1d21712cd23eb428bdc3febe4d047bec115db
Commit Graph
3 Commits
Author SHA1 Message Date
stroblme b7f1d21712 Docs for key renames: ids and keys in the flow concepts, the rename routes, events and 503s in the API reference, hooks during a rename, sync and run metrics after one; a pinned restore refused for its recorded key names that key in the 409
Docs / docs (push) Successful in 3m11s
Details
Playwright Tests / test-playwright (1, 2) (push) Successful in 11m42s
Details
Playwright Tests / test-playwright (2, 2) (push) Successful in 2m22s
Details
pre-commit / pre-commit (push) Successful in 3m12s
Details
Test Backend / test-backend (3.12) (push) Successful in 6m19s
Details
Test Backend / test-backend (3.14) (push) Successful in 5m59s
Details
Compose Smoke Test / test-compose (push) Successful in 37s
Details
Playwright Tests / merge-reports (push) Successful in 1m12s
Details
2026-11-03 08:09:35 +01:00
stroblme d4a1b1db47 History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open 2026-11-02 19:01:19 +01:00
stroblme 08a6376836 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 2026-11-02 17:41:23 +01:00