OplogToRedis: Better Logging for Denylist Failures #95
+3
−1
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.
Summary
When the denylist fails to update due to a database error, the error is now logged.
Jira Task
Level of Impact
Please select exactly one option. To change the level of impact, first unselect the current level of impact and then select the new level of impact.
Impact Analysis
This is a logging only change, and it's not an error level log.
Release Notes
none
Release Change Category
Please select exactly one option. To change the release change category, first unselect the current category and then select the new one.
Feature Flags
none
Test Plan
n/a
Checklist
Check each when they are done or confirmed to not apply. If something here isn't checked, this isn't ready to be merged. Seriously. You are making your colleagues lives a lot easier by doing this consistently. Be a good Tulipian.
For more information on the requirements for every pull request, see Development Definition of Done.