You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multi-node talm apply output prefixes the drift / divergence headers with the node identifier (talm: drift preview (node 192.0.2.10)), but the maintenanceConnectionMessage line that fires on the insecure path is bare:
talm: drift verification unavailable on maintenance connection
talm: drift verification unavailable on maintenance connection
On a multi-node insecure apply (rare — usually only during bootstrap or recovery) the operator sees the same line twice with no way to tell which node it came from. Inconsistent with the per-node-prefixed drift / divergence headers.
Scope: thread nodeID through the existing previewDrift / verifyAppliedState callsites and use the existing nodePrefix helper. One-liner per caller. A pinning test could mirror TestPreviewDrift_MultiNode_HeaderCarriesNodeID with the insecure path branch.
Activity
fix(apply): per-node prefix on insecure path via GlobalArgs.Nodes fal…
fix(apply): Wireguard secret paths + apply-safety-gates test plan rows (
feat(apply,upgrade): apply-safety follow-ups (#189 + #190 + #191 + #192)
feat(apply,upgrade): apply-safety follow-ups (#189 + #190 + #191 + #192)
feat(apply,upgrade): apply-safety follow-ups (#189 + #190 + #191 + #192)
Merge pull request #200 from cozystack/feat/apply-safety-followups