User story #4201
Updated by François ARMAND almost 11 years ago
For new Technique, we provide a template of expected reports in the mean of a CSV file. That file miss generation-time information, like Rule UUID and serial, and Directive UUID. So the expected report build process need to be adapt to parse the CSV template, update missing information, and write the resulting files at the expected place. TODO: * define the CSV template name, and its place (=> expected_report_template.csv) * define the tag name to be replace for serial, rule UUID, directive UUID (=> @@RUDDER_ID@@ ) (@@RULE_ID@@ @@DIRECTIVE_ID@@ @@SERIAL@@) * define the final CSV path (=> expected_report.csv) path. Note: the written CSV must retain all information contained in the source template CSV, especially comments (line starting with #) or headers, if provided.