lab(pod): provisioning preflight — fail on broken file, warn on typos, ship example #289
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_skills!289
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_provisioning_preflight"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to the runtime-configurable provisioning lists. Three changes:
source_note()reports the active source (file vs built-in defaults) so abuild/up no longer silently uses defaults when an operator expected the file.
preflight()runs at the top offlow template install/flow common up:absent file → defaults (opt-in, unchanged); present + valid → used, with a
warning for any repo/service name not in the buildable set /
lab servicemap (catches typos); present + unparseable → hard error instead of silently
shipping the defaults the operator meant to override. Stop/restart paths keep
the lenient fallback (best-effort, shouldn't be blocked by a bad file).
crates/lab/templates/provisioning.toml.example: a commented,copy-paste-ready file next to the existing env.nu / init.sh templates.
Unit-tested (source-note fallback + unknown-name detection).
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com