- possibility to define audited entities

[krzysztofruszczynski]

Hello,
I added possibility to declare only those entities, which we want to log. I combined it with unaudited functionality (only unaudited or audited can be declared - if both are declared, only audited are used). In yml configuration we use similar configuration like for unaudited:

data_dog_audit:
audited_entities:
- AppBundle\Entity\AuditedEntity

[l3pp4rd]

Hi, these both options are conflicting with each other and as a result are confusing. Create a CompilerPass which reads your audited_entity_list, takes all registered metadata from orm, then diffs these class names with your list and adds call method to the audit subscriber to register the unaudited_list.

Adding such option in this bundle, would be more confusing than useful in my opinion. Though I personally would audit everything, and from time to time archive it and reset audit log with the current state of database as version 1.

[markussc]

I think that black- and whitelisting are quite common concepts which should not confuse any user of the bundle.
In our case, we have a very large number of tables (entities), but we only need audit for a small set. Auditing all the tables unnecessarily gives a huge overhead and slows down our system. I think this is a very common use case and would therefore very much appreciate it to be part of the this bundle.

[l3pp4rd]

OK, fine. in most cases I have an audit log for everything and archive the log from time to time, leaving the latest snapshot available in the log. though, there could be a command doing this. the only way to restore data properly is through whole audit log