[WIP] Spike redaction code #128
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* no null constraints on new table for ease of implementation * no faffing with factories yet
jogilder
added
documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
Copy Crime Apply's approach to redacting data.
This spike PR creates a new table 'redacted_submission_versions' which is linked to 'submission_versions'. When we create the submission version, we also create the redacted record with the same attributes. We then run the application data through a set of rules to replace the specified data with the string "redacted".
There is a basic test which validates this behaviour.
Crime Apply's code also has a MetadataWrapper which I have left in the code for now but have commented out as not sure we need it.
Link to relevant ticket
CRM457-
Notes for reviewer
Screenshots of changes (if applicable)
Before changes:
After changes:
How to manually test the feature