feat(devices): show current vs target agent version in Update agent dialog #70

Merged
Claude-Run merged 1 commit from feat/VAPP-61-update-agent-version-display into main 2026-07-01 01:40:27 +02:00
Member

The Update agent modal now shows the device's current agent build (Device::agent_version) alongside the target build it will push to, sourced from the admin-only get_agent_fetcher_config().version. The operator can confirm the update moved the agent forward (current was X, target is Y; the "Agent" fact reads Y after the agent restarts and reconnects).

The target reads as "unknown" when the fetcher config cannot be read (non-admin, read error, or no source configured / disabled), so the modal still opens and the push button stays enabled. When the known target equals the non-empty current build, a brief "already on the target build; the push will skip it" hint renders. The hint is display-only; the server still makes the authoritative skip decision via the pushAgentUpdate ack.

#VAPP-61

The Update agent modal now shows the device's current agent build (Device::agent_version) alongside the target build it will push to, sourced from the admin-only get_agent_fetcher_config().version. The operator can confirm the update moved the agent forward (current was X, target is Y; the "Agent" fact reads Y after the agent restarts and reconnects). The target reads as "unknown" when the fetcher config cannot be read (non-admin, read error, or no source configured / disabled), so the modal still opens and the push button stays enabled. When the known target equals the non-empty current build, a brief "already on the target build; the push will skip it" hint renders. The hint is display-only; the server still makes the authoritative skip decision via the pushAgentUpdate ack. #VAPP-61
feat(devices): show current vs target agent version in Update agent dialog
All checks were successful
Check / fmt + clippy + build + tests (pull_request) Successful in 40s
Create release / Create release from merged PR (pull_request) Has been skipped
676441131f
The Update agent modal now shows the device's current agent build (Device::agent_version) alongside the target build it will push to, sourced from the admin-only get_agent_fetcher_config().version. The operator can confirm the update moved the agent forward (current was X, target is Y; the "Agent" fact reads Y after the agent restarts and reconnects).

The target reads as "unknown" when the fetcher config cannot be read (non-admin, read error, or no source configured / disabled), so the modal still opens and the push button stays enabled. When the known target equals the non-empty current build, a brief "already on the target build; the push will skip it" hint renders. The hint is display-only; the server still makes the authoritative skip decision via the pushAgentUpdate ack.

#VAPP-61
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/vervain-apps!70
No description provided.