Apply

Verify edge coherence for a deploy operation

Probes the project's bound public hosts for mutable static paths changed by an apply or promote operation and reports whether the edge is serving the target release. Promote probes compare the previous live release with the promoted target. Uses release identity headers first, then body hash for responses up to 1 MiB, then weak size/content-type matching. Cross-project operation access returns 403.

get/apply/v1/operations/{operation_id}/edge-coherence

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/apply/v1/operations/{operation_id}/edge-coherence
  • Auth: API key in header apikey

Path parameters

operation_idstring required

Operation ID

Response

Edge coherence report

coherentboolean required
operation_idstring required
project_idstring required

Run402 project ID. Public IDs are not UUIDs.

release_idstring required
release_generationinteger nullable required
pending_countinteger required
paths_truncatedboolean required
path_countinteger required
total_path_countinteger required
vantagestring required
probe_may_have_warmed_cacheboolean required
pointer_updatesEdgePointerUpdates required

Map keyed by edge pointer target. Missing keys mean no outbox row exists for that target.

next_actionsstring[] required
probe_basis'no_mutable_paths'
checked_atstring date-time
verification_basis'no_mutable_paths'

Example response

{
  "project_id": "prj_1741340000_0042",
  "vantage": "gateway-us-east-1"
}

Changes

No recorded changes to this operation across all 1 revision of this API.