release gate
An automatic check that must pass before a change may be deployed.
In more detail
Contract checks make a useful gate: they block a change that would break clients and report which promise it broke. Gates run in the delivery pipeline, so a failing check stops the release automatically.
Example
In Terraform: For Terraform the gate usually requires formatting, validation, tests, policy checks and a reviewed plan, then a named approver before apply runs. GitHub environments with required reviewers are one common way to enforce it.Related terms
- contract testing — Testing that an API’s real behaviour matches its written contract, and that its callers only rely on what the contract promises.
- breaking change — A change that makes existing users of a program or interface stop working until they change something too.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- policy as code — Writing organisational rules, such as required tags or allowed regions, as code that automatically checks every proposed change.
- branch protection rule — A setting on a hosting service that stops changes reaching a branch, usually main, unless conditions such as an approved review and passing checks are met.
- saved plan — A plan written to a file with -out, which terraform apply can later carry out exactly as reviewed.
Taught in
- Contract Testing — Modern API Architecture: REST, GraphQL & gRPC
- Running Terraform In CI — Infrastructure as Code with Terraform
- Native Testing With Tftest Files — Infrastructure as Code with Terraform
- Provider Mocking For Tests — Infrastructure as Code with Terraform
- Policy As Code With OPA — Infrastructure as Code with Terraform
- Releasing The Real Cloud Artifact — Infrastructure as Code with Terraform