-
Notifications
You must be signed in to change notification settings - Fork 166
LG 14123 Include associated user_id in event disavowal CloudWatch logs #11140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
kevinsmaster5
merged 9 commits into
main
from
kmas-lg-14123-include-user-id-event-disavowal
Aug 27, 2024
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
8e30343
changelog: Internal, Fraud prevention, include associated user_id in …
kevinsmaster5 c6f1543
change user.id to use associated user_id
kevinsmaster5 273dd38
move user_id catching to the build_disavowal class
kevinsmaster5 b0f8fdb
add user_id documentation to event
kevinsmaster5 73289ac
fix lint
kevinsmaster5 5df4904
pass user id as uuid
kevinsmaster5 fa5fe08
update specs to use uuid, add nil safe for disavowal error events
kevinsmaster5 2796413
remove nil default
kevinsmaster5 a8d8661
move not-optional keywords
kevinsmaster5 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If you have issues in this spec file after making the changes in my previous comment, I'd consider looking at using the |
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want any changes in this file.
user_idis not meant to be interpreted as a parameter for an individual analytics event, it's available for every analytics event (asproperties.user_id). Properties documented in this file are logged asproperties.event_properties.[property_name], which is not how we'd wantuser_idto be logged.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't tell, but if this is a logged-out event, passing in
user_idlike that makes sense becauseuser.uuidwould beanonymous-uuidor somethingThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to pass it, but I didn't think we'd want to document it here.
That being said, I did a quick audit of if we document it for other methods. It looks like we're not consistent, but document it more often than we don't. (Inconsistency expected since we don't enforce it)
Documented:
remote_logout_completeduser_registration_email_confirmationemail_and_password_authopenid_connect_tokenpassword_creationsecurity_event_receivedidv_doc_auth_submitted_image_upload_formidv_gpo_expiredUndocumented:
add_email_requestpassword_reset_emailpassword_changedidv_doc_auth_failed_image_resubmittedThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I'd guess if we ever wanted to get rid of our
**extrahandling, we'd need to explicitly list all the keyword arguments the method could receive.tl;dr These changes make sense after all 👍