LG-7640 review_status should be a top-level key#7048
Merged
Conversation
theabrad
reviewed
Sep 29, 2022
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
2 participants
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.
🎫 Ticket
LG-7640
🛠 Summary of changes
Add the review status to the top level of the threatmetrix logging results for the following event:
"IdV: in person proofing optional verify_wait submitted"
from here:
properties.event_properties.proofing_results.context.stages.threatmetrix.response_body.review_status
to also here:
properties.event_properties.proofing_results.context.stages.threatmetrix.review_status
because cloudwatch has difficulty parsing large packets at depth
📜 Testing Plan
Provide a checklist of steps to confirm the changes.
👀 Screenshots
🚀 Notes for Deployment
None