Customer wants omnictl cluster template sync --dry-run to show, for each affected machine, whether the proposed cluster template change would require a reboot. This would let them use dry-run output as a CI signal before applying changes through Omni.
Current behavior: dry-run only shows resource-level create/update/delete diffs for Omni resources and does not compute or display reboot impact. Code investigation indicates reboot necessity is determined later by Talos when config is actually applied, so supporting this likely requires a server-side simulation/render path rather than only a CLI formatting change.
Requested outcome: dry-run output should include per-machine reboot impact prediction, ideally in a machine-readable form suitable for CI automation.
Customer wants
omnictl cluster template sync --dry-runto show, for each affected machine, whether the proposed cluster template change would require a reboot. This would let them use dry-run output as a CI signal before applying changes through Omni.Current behavior: dry-run only shows resource-level create/update/delete diffs for Omni resources and does not compute or display reboot impact. Code investigation indicates reboot necessity is determined later by Talos when config is actually applied, so supporting this likely requires a server-side simulation/render path rather than only a CLI formatting change.
Requested outcome: dry-run output should include per-machine reboot impact prediction, ideally in a machine-readable form suitable for CI automation.