turn audit-mode into an full audit-phase where multiple compliance profiles can be executed (current approach with audit cookbook is well perceived, because the execution can be customized, but users need to ensure manually, that it is the last cookbook in the runlist)
be able to run tests located in test/integration directory within that audit phase. That would allow users to reuse the same cookbook tests for test-kitchen and production
@chris-rock this will likely prevent us from getting past the proof of concept of using compliance since our reporting is built on the converged nodes being zero every time. Do you have an idea about priority of this issue and thus a rough timeline?