Output YAML File

3 VersionsOutput

Parses each upstream String (or every element of a [String]) as JSON and writes the result as a YAML document under output_path, with the extension from file_extension and the file named from name_template.

How it fits

Typical backends

Config emission. Serialise a pipeline value to JSON and persist it as a human-editable YAML file.

Format bridge. Pull a structured payload, normalise it to a JSON string, and re-emit it as YAML.

Caveats

FallbackEach input string must be valid JSON; an unparseable string is logged and skipped without advancing the filename index, so it never crashes the sink.
I/O contractAny JSON root shape is accepted — arrays, scalars, and null included — so the output may not load into tools that require a top-level mapping; a list input writes one YAML file per element.
FallbackA leading dot on file_extension is stripped and an empty value falls back to yaml.
State lifetimeThe filename index is a process-local counter that resets on restart, so reusing output_path with the same name_template overwrites earlier files.

Versions

000e3a3fdefault
Automated release
8/1/2026