openapi: document Cloud-runtime request fields on POST /api/assets/export

The Cloud runtime accepts three request fields on /api/assets/export that the
spec didn't declare:

- job_ids: include all assets associated with the given jobs
- naming_strategy: how to name files in the ZIP (enum, default group_by_job_time)
- job_asset_name_filters: optional per-job asset-name allowlist

Also drops asset_ids from required: the runtime supports exporting by job_ids
alone, so neither field is individually required.

/api/assets/export is already x-runtime: [cloud]; these are plain field
additions under that endpoint-level tag.
This commit is contained in:
Matt Miller 2026-05-26 14:24:19 -07:00
parent 011c6bf101
commit 42af952a18

View File

@ -3095,18 +3095,34 @@ paths:
application/json:
schema:
type: object
required:
- asset_ids
properties:
job_ids:
type: array
items:
type: string
description: Job IDs whose associated assets should all be included in the ZIP bundle.
asset_ids:
type: array
items:
type: string
format: uuid
description: IDs of assets to export
description: Asset IDs to include in the ZIP bundle. Additive to assets associated with provided job IDs.
export_name:
type: string
description: Name for the export archive
naming_strategy:
type: string
enum: [group_by_job_id, preserve, asset_id, group_by_job_time]
default: group_by_job_time
description: "Strategy for naming files in the ZIP: group by job ID, preserve original names, use the asset ID, or group by job creation time."
job_asset_name_filters:
type: object
additionalProperties:
type: array
minItems: 1
items:
type: string
description: Optional per-job asset name filters. When provided for a job ID, only assets whose name matches one of the listed names are included.
responses:
"202":
description: Export task accepted