# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Harness Input Sets API
  version: 1.0.0
extends: openapi/harness-input-sets-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: 9
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets'].get
  update:
    x-apievangelist-phrasing:
      intent: List a pipeline's input sets
      effect: read
      questions:
      - Which input sets are saved for one of my pipelines?
      - Can I search a pipeline's input sets by name and sort them?
      instructions:
      - text: List the input sets for pipeline {pipeline} in project {project} of org {org}.
        slots:
          pipeline: query.pipeline
          project: path.project
          org: path.org
      - text: Find input sets on pipeline {pipeline} in {project} whose name matches {search_term}.
        slots:
          pipeline: query.pipeline
          project: path.project
          search_term: query.search_term
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets'].post
  update:
    x-apievangelist-phrasing:
      intent: Create an input set for a pipeline
      effect: write
      questions:
      - How do I save a reusable set of runtime inputs for a pipeline?
      - Can I store a new input set in Git instead of inline?
      instructions:
      - text: Create input set {identifier} named {name} for pipeline {pipeline} in project {project} of {org} using YAML {input_set_yaml}.
        slots:
          identifier: requestBody.identifier
          name: requestBody.name
          pipeline: query.pipeline
          project: path.project
          org: path.org
          input_set_yaml: requestBody.input_set_yaml
      - text: 'Add a new input set {name} to pipeline {pipeline} with this YAML: {input_set_yaml}.'
        slots:
          name: requestBody.name
          pipeline: query.pipeline
          input_set_yaml: requestBody.input_set_yaml
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets/{input-set}'].get
  update:
    x-apievangelist-phrasing:
      intent: Retrieve an input set
      effect: read
      questions:
      - What runtime values does a particular input set supply to my pipeline?
      - Can I load an input set's YAML from a specific Git branch?
      instructions:
      - text: Show input set {input_set} of pipeline {pipeline} in project {project} under {org}.
        slots:
          input_set: path.input-set
          pipeline: query.pipeline
          project: path.project
          org: path.org
      - text: Fetch input set {input_set} for pipeline {pipeline} from branch {branch_name}.
        slots:
          input_set: path.input-set
          pipeline: query.pipeline
          branch_name: query.branch_name
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets/{input-set}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update an input set
      effect: write
      questions:
      - How do I change the values stored in an existing input set?
      - Can I rename an input set I already saved on a pipeline?
      instructions:
      - text: Update input set {input_set} on pipeline {pipeline} in {project} of {org} with YAML {input_set_yaml}.
        slots:
          input_set: path.input-set
          pipeline: query.pipeline
          project: path.project
          org: path.org
          input_set_yaml: requestBody.input_set_yaml
      - text: Rename existing input set {input_set} (id {identifier}) on pipeline {pipeline} to {name}, keeping YAML {input_set_yaml}.
        slots:
          input_set: path.input-set
          identifier: requestBody.identifier
          pipeline: query.pipeline
          name: requestBody.name
          input_set_yaml: requestBody.input_set_yaml
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets/{input-set}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete an input set
      effect: destructive
      questions:
      - How do I remove an input set I no longer need from a pipeline?
      - Can I delete one input set without touching the pipeline itself?
      instructions:
      - text: Delete input set {input_set} from pipeline {pipeline} in project {project} of {org}.
        slots:
          input_set: path.input-set
          pipeline: query.pipeline
          project: path.project
          org: path.org
      - text: Remove the {input_set} input set from pipeline {pipeline}.
        slots:
          input_set: path.input-set
          pipeline: query.pipeline
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets/{input-set}/move-config'].post
  update:
    x-apievangelist-phrasing:
      intent: Move an inline input set to Git
      effect: write
      questions:
      - How do I move an input set stored inline in Harness into a Git repository?
      - Can I convert an inline input set to a remote one?
      instructions:
      - text: Move input set {input_set} in project {project} of {org} from inline to remote Git storage.
        slots:
          input_set: path.input-set
          project: path.project
          org: path.org
      - text: Push the YAML of input set {input_set} for pipeline {pipeline_identifier} to Git with details {git_details}.
        slots:
          input_set: path.input-set
          pipeline_identifier: requestBody.pipeline_identifier
          git_details: requestBody.git_details
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets/{input-set}/import'].post
  update:
    x-apievangelist-phrasing:
      intent: Import an input set from a Git repository
      effect: write
      questions:
      - Can I import an input set YAML that already lives in my Git repo?
      - How do I register a Git-stored input set with a pipeline?
      instructions:
      - text: Import input set {input_set} for pipeline {pipeline} in project {project} of {org} from Git.
        slots:
          input_set: path.input-set
          pipeline: query.pipeline
          project: path.project
          org: path.org
      - text: Pull the input set {input_set} YAML from Git using {git_import_info} and save it for pipeline {pipeline}.
        slots:
          input_set: path.input-set
          git_import_info: requestBody.git_import_info
          pipeline: query.pipeline
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets/{input-set}/git-metadata'].put
  update:
    x-apievangelist-phrasing:
      intent: Update Git metadata of a remote input set
      effect: write
      questions:
      - How do I point a remote input set at a different repo or file path?
      - Can I change the connector used by a Git-backed input set?
      instructions:
      - text: Update the Git metadata of remote input set {input_set} on pipeline {pipeline} in {project} of {org} to repo {repo_name}.
        slots:
          input_set: path.input-set
          pipeline: query.pipeline
          project: path.project
          org: path.org
          repo_name: requestBody.repo_name
      - text: Set file path {file_path} and connector {connector_ref} on remote input set {input_set}.
        slots:
          file_path: requestBody.file_path
          connector_ref: requestBody.connector_ref
          input_set: path.input-set
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/orgs/{org}/projects/{project}/input-sets/merge'].post
  update:
    x-apievangelist-phrasing:
      intent: Merge several input sets for a pipeline
      effect: read
      questions:
      - What do my runtime inputs look like when several input sets are combined?
      - Can I get the merged pipeline YAML for a chosen set of input sets and stages?
      instructions:
      - text: Merge input sets {input_set_references} for pipeline {pipeline} in project {project} of {org}.
        slots:
          input_set_references: requestBody.input_set_references
          pipeline: query.pipeline
          project: path.project
          org: path.org
      - text: Combine input sets {input_set_references} on pipeline {pipeline} for stages {stage_identifiers} only.
        slots:
          input_set_references: requestBody.input_set_references
          pipeline: query.pipeline
          stage_identifiers: requestBody.stage_identifiers
      method: generated
      generated: '2026-09-26'