Version
WEBHOOK

baseline.frozen

The team's approval froze a baseline.

When this fires

The baseline_approval request on the baseline carries, by the approvers' verdicts or by the policy itself. Every item is pinned to its approved version and locked, the requirements and rules among them move to baselined, and from now on a change to anything the baseline holds needs an approved change request.

Related events

  • baseline.signed_off: the client's signature on a scope baseline.
  • change_request.status_changed: a request approved against it unlocks items.

Ability to subscribe

A token needs this to subscribe an endpoint to the event.

Header Parameters

ZG-Signature*string

t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now.

ZG-Event-Id*string

The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.

ZG-Event-Name*string

The event name, the same as the envelope's type.

Content-Type*string

Always application/json.

User-Agent*string

Always ZuseBifrost-Webhooks/1.0.

Payload

JSONWhat Zuse Bifrost posts to your endpoint

The signed JSON envelope posted to your endpoint.

The envelope every event is delivered in.

Responses

2XXAny success status

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

defaultAny other status

Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from Settings → Webhook Deliveries or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.

How is this guide?

Last updated on