feat: mark PII as sensitive in account and user resources. #1678
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
|
Integration tests success for bdf65d612add088273ed2b1cbe780bcff1f4f0bb |
|
Integration tests failure for 9c7880624d0083ba9c066c227542adbbfec04f85 |
sfc-gh-swinkler
approved these changes
Mar 30, 2023
|
Integration tests success for 9c7880624d0083ba9c066c227542adbbfec04f85 |
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.
per European laws, it is not permissible to include PII data in plan output even for employees. Hence it is necessary to mark these fields as sensitive.