Harness · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Harness Slsa V2 API

3 actions 3 updates phrasing extends openapi/harness-slsav2-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for Harness's API. It is a proposal applied on top of the contract, not a document Harness publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info

$.paths['/v2/orgs/{org}/projects/{project}/provenance/{provenance}'].post

$.paths['/v2/orgs/{org}/projects/{project}/slsa-verification/{provenance}'].post

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Harness Slsa V2 API
  version: 1.0.0
extends: openapi/harness-slsav2-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/v2/orgs/{org}/projects/{project}/provenance/{provenance}'].post
  update:
    x-apievangelist-phrasing:
      intent: Save SLSA provenance for an artifact
      effect: write
      questions:
      - How do I record build provenance for an artifact in my project?
      - Can I attach the execution context along with provenance data?
      instructions:
      - text: Save provenance {provenance} with data {data} in project {project} of org {org}.
        slots:
          provenance: path.provenance
          data: requestBody.provenance_data
          project: path.project
          org: path.org
      - text: Record provenance {provenance} for artifact {artifact} in org {org} project {project}.
        slots:
          provenance: path.provenance
          artifact: requestBody.artifact
          org: path.org
          project: path.project
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v2/orgs/{org}/projects/{project}/slsa-verification/{provenance}'].post
  update:
    x-apievangelist-phrasing:
      intent: Save an SLSA verification result
      effect: write
      questions:
      - How do I store whether an artifact passed SLSA verification?
      - Can I record a failed SLSA verification status against its provenance?
      instructions:
      - text: Save SLSA verification status {status} for provenance {provenance} in project {project} of org {org}.
        slots:
          status: requestBody.verification_status
          provenance: path.provenance
          project: path.project
          org: path.org
      - text: Record SLSA verification of provenance {provenance} in org {org} project {project} with data {data}.
        slots:
          provenance: path.provenance
          org: path.org
          project: path.project
          data: requestBody.provenance_data
      method: generated
      generated: '2026-09-26'