This pull request updates the "debug results" that we return from the ImportRockTheVoteRecord@handle method to be a bit more verbose, now that we don't include the email and mobile fields in the base response.
Here's an example from my testing (where it resolved my main user, and a mobile-only test user):
How should this be reviewed?
π
Any background context you want to provide?
This addresses https://github.com/DoSomething/chompy/pull/177#discussion_r453897512. Because we don't return PII in the v2/users response objects, we can no longer easily log the email and mobile fields here. (And because these $user and $this->mobileUser values are queried for all jobs, we don't want to always request those fields since it'd add a ton of noise to our logs.)
To make it as easy as possible to debug jobs locally, this form now prints out the $this->record input values (from the form, which includes any provided PII) alongside the "safe" $user and $this->mobileUser and $post.
What's this PR do?
This pull request updates the "debug results" that we return from the
ImportRockTheVoteRecord@handle
method to be a bit more verbose, now that we don't include theemail
andmobile
fields in the base response.Here's an example from my testing (where it resolved my main user, and a mobile-only test user):
How should this be reviewed?
π
Any background context you want to provide?
This addresses https://github.com/DoSomething/chompy/pull/177#discussion_r453897512. Because we don't return PII in the
v2/users
response objects, we can no longer easily log theemail
andmobile
fields here. (And because these$user
and$this->mobileUser
values are queried for all jobs, we don't want to always request those fields since it'd add a ton of noise to our logs.)To make it as easy as possible to debug jobs locally, this form now prints out the
$this->record
input values (from the form, which includes any provided PII) alongside the "safe"$user
and$this->mobileUser
and$post
.Relevant tickets
References Pivotal #172383688.
Checklist