Read the five gates on a Core digest

product.gates

Returns design review, infosec, SIT, UAT and go-live for the Product's sandbox Core, or the sandbox or live Core coreDigest names. A gate is required when the tenant wrote an approval policy under its key, `core.gate.<gate>`, in this environment, and its state comes from the approvals product.gate.submit opened on that digest, a signed one first, else the newest: open while it waits, signed once every step approved, rejected or returned by a decider, unsubmitted when none waits. Each gate names its policy version, the approval, its steps and every decision. SIT and UAT also name the SHA-256 of the Tests document the stored check outcome renders into. Nothing is stored beside the approvals: a new digest has no approvals, so every gate on it reads unsubmitted.

GET /v1/products/{productId}/gates

Principal api_key. Idempotency not_required. Environment sandbox.

Input

Output

Request sample

curl

curl --request GET 'https://hyperscale0.ai/v1/products/prd_sandbox_00000000000000000001/gates' \
  --header "Authorization: Bearer $HYPERSCALE_API_KEY" \
  --header 'X-Hyperscale-Environment: sandbox'

TypeScript SDK

import { createClient } from "@hyperscale0/sdk";

const hs = createClient({
  apiKey: process.env.HYPERSCALE_API_KEY,
  productId: process.env.HYPERSCALE_PRODUCT_ID,
});
const result = await hs.call("product.gates");

CLI

hyperscale api call product.gates

Errors

All operations