Skip to content

GB-304: grow was given a file that is not a goatlite

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-304 is printed by goatbuilder. The same text offline: goat explain GB-304 or goatbuilder explain GB-304.

What it means

goatbuilder grow hands a goatlite over to the full preset, so it reads goatlite.yaml at the checkout root and needs it to declare preset: lite with a lite: block (ADR 1213). This file declares another preset, or has no lite: block, so there is nothing to grow. A checkout already on the full preset needs no grow. 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 preset: full, or no preset
  • the lite: block is missing or is not a mapping

What to do

One line per step or alternative:

goatbuilder validate goatlite.yaml (it says what the file declares)
a full configuration is ops/goatbuilder/goatbuilder.yaml: goatbuilder validate

Read more

Exit code

goatbuilder exits with 2.