Skip to content
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

Deploy RC 240 to Prod #7568

Merged
merged 10 commits into from
Jan 3, 2023
Merged

Deploy RC 240 to Prod #7568

merged 10 commits into from
Jan 3, 2023

Conversation

solipet
Copy link
Contributor

@solipet solipet commented Jan 3, 2023

Internal

  • Attempts API: Standardize events (#7551)
  • Background Jobs: Move Account Reset job to long running queue (#7556)
  • Background Jobs: Update GoodJob and remove concurrency controls (#7491)
  • Database Optimization: Avoid double-update to doc_auth_logs table (#7550)
  • Dependencies: Update pg gem dependency (#7553)
  • Health Checks: Remove account reset health check (#7548)

ThatSpaceGuy and others added 10 commits December 29, 2022 12:02
changelog: Internal, Attempts API, Standardize events
changelog: Internal, Health Checks, Remove account reset health check
changelog: Internal, Database Optimization, Avoid double-update to doc_auth_logs table
changelog: Internal, Background Jobs, Update GoodJob and remove concurrency controls
changelog: Internal, Dependencies, Update pg gem dependency
changelog: Internal, Background Jobs, Move Account Reset job to long running queue
changelog: Bug Fixes, Identity Verification, Remove ThreatMetrix review redirects
* Remove ThreatMetrix deactivation

changelog: Bug Fixes, Identity Verification, Remove ThreatMetrix deactivation

* remove specs
There were 2 feature flags for ThreatMetrix behavior that conflicted:

- `proofing_device_profiling_decisioning_enabled`: This determined whether or not a user saw the "sad face" screen
- `lexisnexis_threatmetrix_required_to_verify`: This determined whether or not a user received an active profile after successful proofing

There is no case where we want one and not the other or vice versa. Thus this commit merges them into a single `lexisnexis_threatmetrix_required_to_verify` config.

[skip changelog]
These were removed in an attempt to fix an issue where decisioning was enabled (#7560). That change actually did not address the issue. The change in #7562 addressed the issue.

This commit puts this code back.

[skip changelog]
@mitchellhenke
Copy link
Contributor

Can remove the following from the changelog since they were deployed in #7561

Bug Fixes

  • Identity Verification: Remove ThreatMetrix deactivation (#7562)
  • Identity Verification: Remove ThreatMetrix review redirects (#7560)

@solipet
Copy link
Contributor Author

solipet commented Jan 3, 2023

Can remove the following from the changelog since they were deployed in #7561

Updated in the draft release notes

@solipet solipet merged commit 355d96e into stages/prod Jan 3, 2023
@solipet solipet deleted the stages/rc-2023-01-03 branch January 3, 2023 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants