Skip to content

GB-044: a release refuses before the tag because a secret is not set

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

What it means

every rung this run will deploy to templates the component's secrets from your environment, and at least one is not set. Nothing was tagged, pinned or deployed.

Why it happens

  • the run was not wrapped in op run with a .refs file naming those variables
  • goat-credentials refs/goat.refs has no line for a variable (ops/ci/check-secrets-coverage.py names it)

What to do

One line per step or alternative:

put the reference lines for the NOT SET names in .envrc.local.d/<file>.refs, then OP_ACCOUNT=<account> op run --env-file=.envrc.local.d/<file>.refs -- <the same command>

Read more

Exit code

goatbuilder exits with 1.