GB-233: a peering's federation.toml cannot be generated from the environment's¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-233 is printed by goatbuilder. The same text offline: goat explain GB-233 or goatbuilder explain GB-233.
What it means¶
The peering declares federation_toml: rendered, so goatbuilder federate allocate generates its federation.toml from the environment's own ops/federation/<environment>/federation.toml, the one owner of sovereign_id, term_days, cut_contact, the release sets, the accept limits and the measured path MTU, and fills [transport] from the allocated values. That file is missing, is not TOML, or lacks a required top-level value. Nothing was written.
Why it happens¶
- the environment has no ops/federation/<environment>/federation.toml yet
- sovereign_id, term_days or cut_contact is missing from it
What to do¶
One line per step or alternative:
write ops/federation/<environment>/federation.toml once for the environment (the template goat federate init prints is the shape)
or declare federation_toml: hand on the peering and keep writing its federation.toml by hand
Read more¶
Exit code¶
goatbuilder exits with 2.