You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Born from the discussion on #38 , we found that fields_affected in the logs includes data_categories that were not specified on the erasure rule. This is misleading and incorrect.
The logs fields_affected should only output categories that were, in fact, masked by fidesops. This issue should correct the log output and for any other place that the logs incorrectly print what was affected, correct that as well.
The text was updated successfully, but these errors were encountered:
iamkelllly
changed the title
Logs should only output affected
Logs should only output affected data categories
Dec 22, 2021
iamkelllly
changed the title
Logs should only output affected data categories
Logs should only print affected data categories for erasures
Dec 22, 2021
Note, these are the ExecutionLogs that are written to the db-
iamkelllly
changed the title
Logs should only print affected data categories for erasures
DB ExecutionLogs should only print affected data categories for erasures
Dec 22, 2021
* Log just potentially affected fields on the execution logs, rather than all of the fields.
* Add test asserting rules with overlapping data categories don't produce duplicate fields in log.
* Update reporting docs to correct an inaccuracy - queries are not logged in the execution logs, we just have the status of the request and potential fields affected.
- Also have the examples show the in_processing/complete execution logs instead of pending execution logs, because we don't create pending execution logs for an individual collection anymore.
- Privacy requests can also have a "paused" status due to pre-execution policy webhooks
* Add missing backticks around collection names.
* Log just potentially affected fields on the execution logs, rather than all of the fields.
* Add test asserting rules with overlapping data categories don't produce duplicate fields in log.
* Update reporting docs to correct an inaccuracy - queries are not logged in the execution logs, we just have the status of the request and potential fields affected.
- Also have the examples show the in_processing/complete execution logs instead of pending execution logs, because we don't create pending execution logs for an individual collection anymore.
- Privacy requests can also have a "paused" status due to pre-execution policy webhooks
* Add missing backticks around collection names.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Born from the discussion on #38 , we found that
fields_affected
in the logs includesdata_categories
that were not specified on the erasure rule. This is misleading and incorrect.The logs
fields_affected
should only output categories that were, in fact, masked by fidesops. This issue should correct the log output and for any other place that the logs incorrectly print what was affected, correct that as well.The text was updated successfully, but these errors were encountered: