Dolby OptiView Inspect an Engine's Last Run

arazzo: 1.0.1
info:
  title: Dolby OptiView Inspect an Engine's Last Run
  summary: Pick an engine on a channel, fetch its most recent run, then list its full run history.
  description: >-
    Drills into the run history of a single transcoding engine. The workflow
    lists the engines on a channel, selects the first one, fetches that engine's
    most recent run (start, stop, and configuration), and then lists the engine's
    complete run history. The three read operations chain on the engine id so a
    single pass yields both the latest run and the full timeline. Every step
    inlines its Authorization header so the flow can be read and executed without
    opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: channelsApi
  url: ../openapi/dolby-io-channels-api-openapi.yml
  type: openapi
- name: enginesApi
  url: ../openapi/dolby-io-engines-api-openapi.yml
  type: openapi
workflows:
- workflowId: inspect-engine-last-run
  summary: Resolve an engine, read its last run, and list all of its runs.
  description: >-
    Lists a channel's engines, then reads the last run and the full run history
    of the first engine.
  inputs:
    type: object
    required:
    - authorization
    - channelId
    properties:
      authorization:
        type: string
        description: HTTP Basic Authorization header value.
      channelId:
        type: string
        description: The id of the channel whose engine should be inspected.
  steps:
  - stepId: listEngines
    description: List the channel's engines and capture the id of the first engine.
    operationId: get-channel-engines
    parameters:
    - name: id
      in: path
      value: $inputs.channelId
    - name: Authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      engineId: $response.body#/data/0/id
  - stepId: getLastRun
    description: >-
      Fetch the engine's most recent run. The run object includes engineId,
      start, config, and startType under data.
    operationId: get-engine-last-run
    parameters:
    - name: id
      in: path
      value: $steps.listEngines.outputs.engineId
    - name: Authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      lastRunStart: $response.body#/data/start
      lastRunEngineId: $response.body#/data/engineId
  - stepId: listRuns
    description: List the full run history for the engine.
    operationId: get-engine-runs
    parameters:
    - name: id
      in: path
      value: $steps.listEngines.outputs.engineId
    - name: Authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      runs: $response.body#/data
  outputs:
    engineId: $steps.listEngines.outputs.engineId
    lastRunStart: $steps.getLastRun.outputs.lastRunStart
    runs: $steps.listRuns.outputs.runs