Harness · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Harness Anomaly Comments API

3 actions 3 updates phrasing extends openapi/harness-anomaly-comments-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['/ccm/api/anomaly/v2/comment'].get
$.paths['/ccm/api/anomaly/v2/comment'].post

OpenAPI Overlay

Raw ↑ 
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Harness Anomaly Comments API
  version: 1.0.0
extends: openapi/harness-anomaly-comments-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['/ccm/api/anomaly/v2/comment'].get
  update:
    x-apievangelist-phrasing:
      intent: List comments on a cost anomaly
      effect: read
      questions:
      - What has the team said about a particular cost anomaly?
      - Can I read the discussion history on a cloud spend anomaly?
      instructions:
      - text: List comments on cost anomaly {anomalyId}.
        slots:
          anomalyId: query.anomalyId
      - text: Show the notes left on anomaly {anomalyId}.
        slots:
          anomalyId: query.anomalyId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/ccm/api/anomaly/v2/comment'].post
  update:
    x-apievangelist-phrasing:
      intent: Comment on a cost anomaly
      effect: write
      questions:
      - Can I annotate a cost anomaly with an explanation?
      - Is it possible to record why a spend spike happened on the anomaly itself?
      instructions:
      - text: Add comment {comment} to anomaly {anomalyId} in account {accountId}.
        slots:
          comment: requestBody.comment
          anomalyId: requestBody.anomalyId
          accountId: requestBody.accountId
      - text: Note on anomaly {anomalyId} for account {accountId} that {comment}.
        slots:
          anomalyId: requestBody.anomalyId
          accountId: requestBody.accountId
          comment: requestBody.comment
      method: generated
      generated: '2026-09-26'