Customers should know what input was replaced with what output and under which detector (eg regex, or ip_address). We thus need to write out a report at the end of the must-gather-clean process that will contain:

• for each obfuscator: the replacement map (input -> output)
• for each omission: what files were omitted
• what files were processed

The reporting format must be easily machine+human readable (eg json or yaml) for re-invocations of the must-gather CLI (more info in CFE-31) 

AC:

• invocation of the must-gather-clean cli should always write a report into the current working directory 
• report should be machine and readable