Release gate: go or no-go

A release gate is a list of rules over the key metrics of your evidence. Open the template Release gate: API and infrastructure: two OpenAPI version pairs, two Terraform plans and the dbt lineage of a revenue report. Press Run all.

1. Read the verdict

Go to Release gate (press 7). The banner says No-go: at least one rule fails. Each row shows the rule, the Current value and Pass or Fail:

• OpenAPI change: Breaking changes at most 0 — current value 4, from Shop API: current → candidate,
• Terraform plan: Critical-risk changes at most 0 — 2, from AWS production plan,
• Terraform plan: To destroy at most 0 — 1,
• Terraform plan: Drifted resources at most 0 — 2,
• OpenAPI change: Documentation issues at most 5 — 3, Pass.

When several items have the same kind, the worst value counts and its title is shown next to the value.

2. See what blocks it

Under the rules, findings behind the failing rules lists the open findings of the evidence that made each rule fail, critical first: Terraform will replace aws_db_instance.main. (a stateful database), Breaking change at DELETE /orders/{id}: operation removed. and The new spec has breaking changes but keeps the major version 1.0.0; release it as a new major version.

Resolve or ignore a finding on the Findings page and the rules on open findings update at once. Rules on tool metrics change when the evidence changes and you run it again.

3. Build your own rules

• Suggest rules adds sensible defaults for the kinds in your deck (no open critical findings, no breaking changes, no Terraform drift, CI failure rate at most 20 %, no Lambda timeouts …).
• Add rule adds a row; pick the Metric, at most or at least, and the Limit.
• Untick On to keep a rule without enforcing it.

The gate says Go only when every active rule has a result and passes; with missing results it says Incomplete. Copy verdict as text copies a short summary for your release ticket.