Documentation
¶
Overview ¶
Command audit_conversion reports the data_conversion nodes whose behaviour changed when an unresolvable field stopped being a silent no-op.
Before that change a field name that resolved to nothing returned the message unchanged, with no error. It is now a conversion failure following the node's Error Behaviour, and the editor defaults that to "fail" -- so a node that has been quietly doing nothing starts failing its workflow.
This finds those nodes. It cannot prove a field resolves at runtime, because that depends on the live message, so it uses the best evidence in storage: the source's stored Sample, which is the same thing the editor builds its field list from. A field absent from the Sample is the shape that was silently doing nothing.
go run ./scripts/audit_conversion -dsn '/path/to/hermod.db' go run ./scripts/audit_conversion -driver pgx -dsn 'postgres://...'