This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Adds the Null Masking Strategy and Clarifies Supported Policy Masking Strategies [SOL-273] #3
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.
Purpose
Our first iteration of erasure policies only supports masking customer data with null values. Add an official Null Masking Strategy and clarify that other masking strategies will be supported in the next release. There are many masking strategies available directly in the masking service, however.
Changes
MaskingAPIResponse
schema to allow null values as the masked value (currently used in the masking service)Ticket
https://ethyca.atlassian.net/browse/SOL-273