Trace a pull request's gate requirement result

Compare the environment assessment for the reviewed commit with the delivery target's confirmed requirements to identify which service caused a violation or left a check incomplete.

Read the assessment result#

When Proofline assesses the environment on a pull request's review, it checks each confirmed requirement of the repository's delivery target over the evidence the assessment pinned: a requirement that names a service against that service alone, and any other against every service the target binds. Each requirement gets one result:

  • Satisfied when every service it is checked against meets it.
  • Violated when a service does not. Proofline reports it as a finding of the environment in the Proofline check and the pull request comment, with the service, the requirement's values and why it fails. The finding names the confirmed gate requirement as its source and links to the delivery target's gate requirements. A later push that still violates the same requirement does not repeat the finding. A missing required key that the pull request itself adds to the service, provided as the requirement says, is not reported. Neither is a violated ECS capacity requirement, or a required key provided as a Secrets Manager secret or SSM parameter, when Terraform files the pull request changes meet it on every service that violates it: they give the service the capacity the requirement asks for, or take the key from the store the requirement names. The pull request must add that Terraform; when the Terraform already stated the value before the pull request, the violation is reported.
  • Not established when the evidence cannot show either. The pull request does not mention it, and it never counts as satisfied. On the gate requirements page, the requirement shows Not checked on the latest pull request with the reason, and the Inbox shows a row for the delivery target, as Open the gate requirements describes.

On the gate requirements page, each confirmed requirement shows its result on the latest pull request that checked it. Latest pull request links to that pull request's review and says when Proofline checked it. Result reads Satisfied or Violated, with Proofline's Explanation, and a violation names the Service, or the Cloud Run Revision, that does not meet it. A missing key that the pull request itself adds reads Violated; the pull request sets it.

A proposal is never checked. Confirming or withdrawing a requirement leaves results already recorded unchanged; the next review checks the requirements confirmed at that time.

Search help

Tab to a result. Enter to open. Escape to close.