-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add recordTransformation to DLP with cryptoDeterministicConfig support #9836
add recordTransformation to DLP with cryptoDeterministicConfig support #9836
Comments
I just got a notification about this issue but I can't see what it was 😅 This issue is requesting two things: 1) adding record transformations e.g. Completed in PRs:
This is shown in the provider documentation here: 2) Adding cryptoDeterministicConfig support. e.g. This hasn't been completed yet; the |
I was working on another issue regarding |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
In relation to #9108, adding the cryptoDeterministicConfig for tabular and structured data would be helpful, as well. Learn more about tabular data transformation in the examples of de-identifying tabular docs.
De-identifying tabular data is handled by the
recordTransoformation
attributes, which will eventually have the sameinfo_type_transformation
block with primitive crypto types.An example from the docs is in the references section.
New or Affected Resource(s)
Potential Terraform Configuration
The below example shows performing deterministic crypto for 2 columns and applying the transform to the entirety of the columns. It also shows applying a deterministic crypto for 1 column while looking for 2 particular info types and leaving the rest of the column unchanged.
References
DLP de-identification API Overview
DLP record transformation guide
example java example for DLP handling table data through record transformations
#0000
The text was updated successfully, but these errors were encountered: