Add runtime observation and systemd restart adapter
This commit is contained in:
@@ -103,3 +103,16 @@ WireGuard or systemd operation, does not provide concurrent-editor locking,
|
||||
and is not automatic rollback after a failed runtime restart. The separate
|
||||
pre-operation archive remains the recovery source if local journal data is
|
||||
unusable; the adapter does not silently discard an invalid journal.
|
||||
|
||||
For an explicit restart, the application creates the pre-restart archive before
|
||||
calling the service adapter. After a successful terminal service job, it checks
|
||||
the complete observed peer set against the saved server document. A match is
|
||||
then recorded by installing the updated `internal-state.toml` through this same
|
||||
journal, with reservations removed only from the proposed state as appropriate.
|
||||
The in-memory saved/applied state advances only after installation succeeds. If
|
||||
that write or journal recovery fails after the VPN may have changed, the
|
||||
application reports the persistence stage, retains in-memory reservations, and
|
||||
requires manual recovery; it does not roll back or restart again. Default tests
|
||||
exercise this orchestration with private fake adapters and synthetic files.
|
||||
Actual interface and systemd behavior remain deferred to the isolated Alpine
|
||||
and disposable VM acceptance environments described in `RUNTIME.md`.
|
||||
|
||||
Reference in New Issue
Block a user