Closed jongpie closed 2 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 93.16%. Comparing base (
2894401
) to head (6d7d04a
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Core Unlocked Package Changes
🐞 Fixed #542 (almost exactly 1 year after it was opened😅) to use a more targeted regular expression for identifying US social security numbers (SSN) to mask. Previously, the rule was not restrictive enough in the regular expression used in
SensitiveDataRegEx__c
, which resulted in the rule masking some values that it should have ignored.For example, logging a message containing a (fake) credit card number like
Here is a value 5000-1111-2222-0005 and it looks like a Mastercard number, so apply the Mastercard masking rule
...Here is a value XXX-XX-1111-2222-0005 and it looks like a Mastercard number, so apply the Mastercard masking rule
Here is a value ****-****-****-0005 and it looks like a Mastercard number, so apply the Mastercard masking rule
🤏 And a little bit of scope creep included:
ComponentLogger
to cache the field map forLogEntryEvent__e
once per transactionv4.14.6
ComponentLogger
would re-call the describe method forLogEntryEvent__e
every time there was a component log entry that was setting 1 or more custom fieldsPipeline Changes
scripts/build/validate-custom-metadata-records.apex
to validate that the regex values inLogEntryDataMaskRule__mdt
work as expected