GB-306: the full configuration grown from a goatlite is incomplete¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-306 is printed by goatbuilder. The same text offline: goat explain GB-306 or goatbuilder explain GB-306.
What it means¶
goatbuilder grow rewrote goatlite.yaml as a full configuration, and the result fails the schema or a cross-field rule, so it was not written. Most often the goatlite is the four-fact file of the tutorial: the lite preset took repo and components from the checkout, and a full configuration declares its own. The message lists each problem and names the fields to add. grow changes files in the checkout only, never a host: a finished grow is undone with git before it is committed (restore goatlite.yaml and the files whose generated header it took off, and delete ops/goatbuilder/goatbuilder.yaml), and goatbuilder grow --dry-run shows every write first.
Why it happens¶
- goatlite.yaml declares no repo or components, and the checkout has no configuration to take them from
- a value in goatlite.yaml is valid for the lite preset but not in the full shape (the message names it)
What to do¶
One line per step or alternative:
add repo: and components: to goatlite.yaml (the fixture ops/goatbuilder/fixtures/goatnet-from-scratch/00-goatlite shows both), then goatbuilder grow --dry-run
Read more¶
Exit code¶
goatbuilder exits with 1.