fix: approval-route ordering (missed by #6) + remove-offline-node action #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/remove-offline-node"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two changes, one of them a fix for a bug currently live on
main.1. Route-order fix (was missed by PR #6's merge)
GET /api/nodes/pendingwas declared afterGET /api/nodes/:id, so Sinatramatched
pendingas an:id→ 404, and the "Nodes awaiting approval" sectionnever rendered. This fix (declaring the enrollment/approval routes before
:id)was pushed to PR #6 after it was merged, so it didn't ship — the approval UI is
currently broken on production. This PR carries it.
2. Remove-offline-node action
Clears a stale/offline node (e.g. the pre-keypair citadel duplicate left by the
identity migration) from the UI without touching the DB.
node_repository.deleteremoves the node row + its derived rows (node_filescache, queued node_commands).
DELETE /api/nodes/:id(session-authed, write role, main only) — refuses themain self-node (409). A still-live node just re-enrols as pending next check-in.
Full suite green — 1118 examples, 0 failures.
After merge: the approval section will work, and you can Remove the stale citadel
row once the real (keypair) citadel is approved.
🤖 Generated with Claude Code