RFC: Report pending app config changes in ZInfoApp - #158
Draft
christoph-zededa wants to merge 2 commits into
Draft
RFC: Report pending app config changes in ZInfoApp#158christoph-zededa wants to merge 2 commits into
christoph-zededa wants to merge 2 commits into
Conversation
EVE stages some accepted config changes instead of applying them to a running app instance: since lf-edge/eve#6188 and lf-edge/eve#6433 a change to an app's virtual or passthrough network adapters no longer purges the app, but takes effect only on the next app restart. The device acks the new config version in appVersion and keeps reporting the app as RUNNING, so the controller cannot distinguish "applied" from "accepted but staged until restart". Add a pending_changes list to ZInfoApp carrying a human-readable description of each staged change; an empty list means the running instance matches the current config. The description is wrapped in a message so the report can grow (kind, staged-since timestamp, required action) without claiming new ZInfoApp field tags. Requested in lf-edge/eve#6433 (comment) Signed-off-by: Christoph Ostarek <christoph@zededa.com>
Signed-off-by: Christoph Ostarek <christoph@zededa.com>
christoph-zededa
force-pushed
the
app_pending_changes
branch
from
September 7, 2026 13:22
1d52200 to
0643683
Compare
christoph-zededa
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EVE stages some accepted config changes instead of applying them to a running app instance: since lf-edge/eve#6188 and lf-edge/eve#6433 a change to an app's virtual or passthrough network adapters no longer purges the app, but takes effect only on the next app restart.
The device acks the new config version in appVersion and keeps reporting the app as RUNNING, so the controller cannot distinguish "applied" from "accepted but staged until restart". Add a pending_changes list to ZInfoApp carrying a human-readable description of each staged change; an empty list means the running instance matches the current config. The description is wrapped in a message so the report can grow (kind, staged-since timestamp, required action) without claiming new ZInfoApp field tags.
Requested in
lf-edge/eve#6433 (comment)