Harness · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Harness CACM global cost settings API

3 actions 3 updates phrasing extends openapi/harness-cacm-global-cost-settings-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/cost-settings'].get
$.paths['/ccm/api/cost-settings'].put

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 CACM global cost settings API
  version: 1.0.0
extends: openapi/harness-cacm-global-cost-settings-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/cost-settings'].get
  update:
    x-apievangelist-phrasing:
      intent: Get cost settings for a cost management feature
      effect: read
      questions:
      - Which AWS cost type, such as amortized or net, does a cloud cost feature use?
      - Are AWS benefits included in the cost settings for this feature?
      instructions:
      - text: Get the cost settings for feature {feature}.
        slots:
          feature: query.feature
      - text: Show which cost types feature {feature} uses in account {account}.
        slots:
          feature: query.feature
          account: query.accountIdentifier
      method: generated
      generated: '2026-09-26'
- target: $.paths['/ccm/api/cost-settings'].put
  update:
    x-apievangelist-phrasing:
      intent: Change cost settings for a cost management feature
      effect: write
      questions:
      - How do I switch a cloud cost feature to show amortized AWS costs?
      - Can I set different cost types for Azure and GCP on the same feature?
      instructions:
      - text: Set AWS cost type to {aws_type} for feature {feature}.
        slots:
          aws_type: requestBody.awsCostType
          feature: requestBody.feature
      - text: Update feature {feature} to use {aws_type} for AWS and {azure_type} for Azure.
        slots:
          feature: requestBody.feature
          aws_type: requestBody.awsCostType
          azure_type: requestBody.azureCostType
      method: generated
      generated: '2026-09-26'