Boot a QEMU router from example-router.toml in release validation #119

Open
opened 2026-11-10 17:54:32 +01:00 by Alex · 0 comments
Owner

Problem

  • example-router.toml is the reference startup template. Today only Go unit tests check it: it is current, it covers every option, and it imports with test credentials.
  • No test boots a router from it, so a template that passes the unit tests but fails at first boot goes unnoticed until a user tries it.

Goal

  • Release validation boots a factory QEMU router from example-router.toml, changed only as the file's own header instructs (target MACs, required secrets), and checks the exported configuration and first-boot history.
  • Not part of per-PR checks (runtime cost).
## Problem - `example-router.toml` is the reference startup template. Today only Go unit tests check it: it is current, it covers every option, and it imports with test credentials. - No test boots a router from it, so a template that passes the unit tests but fails at first boot goes unnoticed until a user tries it. ## Goal - Release validation boots a factory QEMU router from `example-router.toml`, changed only as the file's own header instructs (target MACs, required secrets), and checks the exported configuration and first-boot history. - Not part of per-PR checks (runtime cost).
Sign in to join this conversation.
No labels
No milestone
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
Alex/kaido-core#119
No description provided.