The output value should be defined before usage.
| Arazzo | Compatibility |
|---|---|
| 1.x | ✅ |
In Arazzo, every outputs mapping—linking a friendly name to a dynamic output value—must be explicitly defined before it is referenced or used elsewhere in the description.
| Option | Type | Description |
|---|---|---|
| severity | string | Possible values: off, warn, error. Default off. |
An example configuration:
rules:
outputs-defined: errorGiven the following configuration:
rules:
outputs-defined: errorExample of a correct outputs description:
workflows:
- workflowId: events-crud
steps:
- stepId: create-event
operationPath: $sourceDescriptions.museum-api#/paths/~1special-events/post
requestBody:
payload:
name: 'Mermaid Treasure Identification and Analysis'
description: 'Identify and analyze mermaid treasures'
outputs:
specialEventId: $response.body#/id
outputs:
createdEventId: $steps.create-event.outputs.specialEventId