Scaffold and validate a playbook
§ 1Purpose
Start a new playbook from the built-in skeleton and confirm it validates before running anything.
§ 2Prerequisites
- The config-weave binary is on PATH.
§ 3Flowchart
§ 4Steps
§ 4.11
§ 4.2Scaffold a skeleton
$ config-weave init ./my-playbook
created ./my-playbook (playbook.wcl, pkgs/core/…)
Run config-weave init ./my-playbook. It writes a skeleton playbook with an example package, resource and gatherer — a working starting point.
§ 4.32
§ 4.4Validate the whole pipeline
$ config-weave validate ./my-playbook
ok
What validate covers
WCL syntax, schema, ref resolution, the step DAG, and wscript compilation of every script — host-API misuse is caught here, before any execution.
Run config-weave validate ./my-playbook. Nothing executes; fix any reported syntax, schema, ref, DAG or script-compilation error before moving on.
§ 4.53
§ 4.6List the plays
$ config-weave list ./my-playbook
baseline
Run config-weave list ./my-playbook to see the plays you can check or apply.
Verification
config-weave validate exits 0 and list prints the expected play names.