Configuration Management

Config diff and rollback

Each gateway's staged config version and whether it has been confirmed applied. Open a row's diff to see that node's config history version by version, and roll back to an earlier one — rollback is recorded as a new forward version, history is never rewritten.

Status · Live

Configuration status

Each device's latest staged config and whether it has been confirmed applied. "Staged, unconfirmed" covers both still-in-flight and stuck candidates -- the cloud cannot currently distinguish those two. "Diff & rollback" opens that device's own NODE's config history -- every other device under the same node shares that history.

Loading…

Primary · Configuration

Config drift policy

Full drift detection is not built: there is no channel for a gateway to report its own live config back to the cloud, so there is nothing to diff against the last-applied config. This toggle and the score below are real, but neither can act on a true device-reported drift signal yet.

Loading…

Not built yet.

A config-apply approval workflow (a second principal must sign off before a staged config actually applies) does not exist. The RBAC grant-request workflow (JIT & break-glass tab, Authorization page) approves a time-bound ROLE grant, not a config version or an apply action -- it is a different, already-built feature, not this one under another name. Any operator at a node can roll back, apply a golden-config template, or run a bulk push immediately today, with no gate. This needs real decisions this app doesn't have yet (who approves, per-node or per-role, does it block Run or just warn, does bulk push route through it too) -- flagged for Siddharth rather than invented.