Output TOML File

2 VersionsOutput

Serialises each upstream record (generic { $ns: $ts... }) to a TOML document under output_path, mapping records to tables, lists to arrays, and scalars to their TOML counterparts, one file per call named from name_template.

How it fits

Typical backends

Config snapshot. Build a structured record per run and persist it as a human-editable TOML file.

Format bridge. Parse an inbound JSON payload, reshape it, and re-emit it as TOML.

Caveats

AccuracyUnsigned integer fields are narrowed to signed 64-bit, byte values are written as base64 strings, and a single character becomes a one-character string; a value whose type has no TOML representation aborts the write.
I/O contractThe whole record is serialised atomically — a value the encoder cannot handle fails the call rather than producing a partial file.
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

dc6d0aabdefault
Automated release
8/1/2026