Conversation
require File.expand_path(support) | ||
end | ||
|
||
Retries.sleep_enabled = false |
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.
This line is basically why I opted to use retries
gem over Faraday's retrying -- I could not find any indication that Faraday would let us "cancel" sleeps in tests, so this lets us test our logic in specs without slowing them down or adding a lot of extra config logic
'lexisnexis_account_id' => 'abc123', | ||
'lexisnexis_request_mode' => 'aaa', | ||
'lexisnexis_username' => 'aaa', | ||
'lexisnexis_password' => 'aaa', | ||
'lexisnexis_base_url' => 'https://lexisnexis.example.com/', | ||
'lexisnexis_phone_finder_workflow' => 'aaa', |
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.
definitely looking forward to a day when we can pass these all in to the gems as explicit params instead of relying on ENV vars
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.
Looks good to me 👍🏼
(I also scaffolded out a ProofResolution that I removed in 3d47d11, because I figure the structure of the two will match, so I wanted to get feedback on this approach first
The gist right now is:
Inputs to the lambda:
Lambda result (aka response):
POSTs to
$callback_url
with a body like this (it'sProofer::Result#to_h
as JSON)headers:
X-API-AUTH-TOKEN
: shared secret with IDP (may need to differ per env)body: