Validate Attestation Occurrence

binary_authorization.validate_attestation_occurrence

ActionGoogle Cloudconnection required

Calls Binary Authorization POST /v1/projects/{projectsId}/attestors/{attestorsId}:validateAttestationOccurrence.

Returns whether the given Attestation for the given image URI was signed by the given…

Ask about Google Binary Authorization All Google Binary Authorization nodes Provider API docs ↗

Connection

Required: Yes — the node will not save without one
Auth type: OAuth 2.0
Providers: Google Binary Authorization
Secret shape: {"client_id", "client_secret", "refresh_token"}
Config it needs: project_id
Resolved by: config.connection_id, else node.connection_id

Configuration

3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
project_id GCP project id (overrides connection).	string	No	—	—	—
attestor Id of the attestor to act on, from binary_authorization.list_attestors — not its name.	string	Yes	—	—	—
body Request body (ValidateAttestationOccurrenceRequest) as JSON.	object	No	—	—	—

Output

One shape.

result

Field	Type	Example
ok	boolean	—
result	string	—
denialReason	string	—

{
  "denialReason": "",
  "ok": false,
  "result": ""
}

Related Google Binary Authorization nodes

See Validate Attestation Occurrence run in a workflow.

In a technical demo we add the Google Binary Authorization connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demo Talk to sales