Skip to content

GB-200: the federation plan's inputs changed

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

What it means

an input the saved plan rests on (versions, the agreement, a rendered file, a certificate, a resource or the acceptance policy) differs from what the plan recorded, so the approval given to that plan does not cover this change.

Why it happens

  • a phase rendered, minted or composed again after the plan was made
  • the checkout, the goat binary or a declared value changed after the plan was made

What to do

One line per step or alternative:

goatbuilder federate plan <partner>, then review and approve the new plan

Read more

Exit code

goatbuilder exits with 1.