2026-11-04 21:20:29 +01:00
..
2026-11-03 08:09:35 +01:00
2026-10-15 15:48:22 +02:00
2026-11-04 21:20:29 +01:00
2026-11-02 19:39:14 +01:00
2026-11-02 19:39:14 +01:00
2026-11-02 21:30:01 +01:00
2026-10-16 11:40:02 +02:00
2026-11-02 19:14:59 +01:00
2026-10-28 08:41:52 +01:00
2026-10-15 17:37:56 +02:00
2026-10-28 12:46:42 +01:00
2026-11-02 19:01:19 +01:00
Rename orchestration, splice and routes: a Renamer runs one rename at a time, closing the gate, taking the controller lock and holding the engine, each waiting without a limit and saying what it waits for (summary rename status, rename_waiting); DELETE on the pending request or a closed connection calls it off until the journal begins (409 aborted); then journal, steps and audit, retried in the background on failure (503 completing); splice_renamed rebuilds the affected flows under the held lock keeping stopped, paused and parked work, history limits and device wiring refreshed before activation; AlertManager.rename and EventBus.rename/settle follow the names; flow and dashboard rename routes answer by code and repeat stored results; renamed, dashboard_changed and pipeline_rebuilt after release; fluksio serve reads flow files without building a FlowStore
2026-11-02 22:14:44 +01:00
2026-11-02 17:41:23 +01:00
2026-10-06 17:19:48 +02:00
2026-11-02 19:01:19 +01:00
2026-11-02 19:01:19 +01:00
2026-08-24 18:17:16 +02:00
2026-11-02 21:30:01 +01:00
Rename planner and document rewrite: rewrite_documents moves qualified names of the renamed flow in every flow (ports, inputs, outputs) and dashboard binding (one key table, WIDGET_BINDINGS, shared with the WidgetDef accessors, legacy pages included), published and draft, as plain JSON with both variants above either version; plan_rename reports documents, counts, fingerprint, warnings and refusals; superuser plan routes for flows and dashboards; key residue classifies state as the mapper does; duplicate retargets inputs and outputs too; queue reports its Redis version and other consumers
2026-11-02 21:06:39 +01:00
Rename orchestration, splice and routes: a Renamer runs one rename at a time, closing the gate, taking the controller lock and holding the engine, each waiting without a limit and saying what it waits for (summary rename status, rename_waiting); DELETE on the pending request or a closed connection calls it off until the journal begins (409 aborted); then journal, steps and audit, retried in the background on failure (503 completing); splice_renamed rebuilds the affected flows under the held lock keeping stopped, paused and parked work, history limits and device wiring refreshed before activation; AlertManager.rename and EventBus.rename/settle follow the names; flow and dashboard rename routes answer by code and repeat stored results; renamed, dashboard_changed and pipeline_rebuilt after release; fluksio serve reads flow files without building a FlowStore
2026-11-02 22:14:44 +01:00
2026-10-29 14:24:17 +01:00
2026-11-02 19:14:59 +01:00
2026-08-30 12:51:08 +02:00
2026-10-15 11:00:19 +02:00