Stricter data protection errors#7837
Draft
justindbaur wants to merge 4 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7837 +/- ##
==========================================
- Coverage 61.23% 61.19% -0.04%
==========================================
Files 2209 2210 +1
Lines 97743 97754 +11
Branches 8815 8815
==========================================
- Hits 59849 59819 -30
- Misses 35770 35810 +40
- Partials 2124 2125 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This file contains hidden or 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
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.



🎟️ Tracking
📔 Objective
Add stricter and early exception when there are issues with getting certificates used in data protection. Before the
CoreHelpersmethod we used would just completely swallow load errors and return null. The null in the case of protection certificates would result in aArgumentNullExceptionand null in the unprotect case would cause a delayedNullReferenceExceptionwhen the first piece of data is unprotected.This also removes the use of async over sync.
📸 Screenshots