FDP_Value will contain an empty string.
YAML Path expressions use dotted property paths (for example metadata.name or store.bicycle.color). An optional $. prefix is accepted for familiarity with JSONPath. Multi-document YAML is supported; use filters such as (kind == Service).metadata.name to select a document.
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
YAML Source |
| Yes | YAML Source to parse. For example, a Kubernetes manifest or variable containing YAML content. Multi-document YAML is supported (use filters such as |
YAML Path Expression |
| Yes | The YAML Path expression to use to find a value in the YAML Source (e.g. |
Require non-blank Output |
| No | If checked, the output must be non-blank at the end of execution or the execution will fail. @Since 11.2.0.0 |
Outputs
Output Name | Required | Description |
|---|---|---|
| No | The value returned from the YAML Path expression is returned to the workflow in this variable. @Since 11.2.0.0 |
Artifacts
This operation doesn’t consume or produce any artifacts.Endpoint Selection
This operation will select all available endpoints associated to the Target.Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.Special Considerations
-
If multiple elements match the criteria, they will be returned in a set-style string (the result of Java
Set.toString()). - Invalid YAML fails the step with a clear error.
- Blank YAML Source or blank YAML Path Expression fails validation.