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

Bdex/54161: Migrate eVSS calls to rated disabilities functionality (vets-api /rated_disabilities) #12234

Merged
merged 0 commits into from
Apr 14, 2023

Conversation

sethdarragile6
Copy link
Contributor

Summary

  • This PR migrates eVSS calls to rated disabilities functionality to Lighthouse (or any provider!)
  • Created by: Benefit Delivery Experience team
  • Flipper switch 'disability_compensation_lighthouse_rated_disabilities_provider' should be enabled when LH migration goes live, then removed once functionality is verified

Related issue(s)

Testing done

  • Unit tests for factory, provider and service created. Also manually tested via Postman and using the local instance of vets-website

What areas of the site does it impact?

Disability claims

Acceptance criteria

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No error nor warning in the console.
  • Events are being sent to the appropriate logging solution
  • Documentation has been updated (link to documentation)
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)
  • If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
  • I added a screenshot of the developed feature

@github-actions
Copy link

github-actions bot commented Mar 23, 2023

1 Warning
⚠️ This PR changes 332 LoC (not counting whitespace/newlines).

In order to ensure each PR receives the proper attention it deserves, we recommend not exceeding
200. Expect some delays getting reviews.

File Summary

Files

  • app/controllers/v0/disability_compensation_forms_controller.rb (+1/-8)

  • app/controllers/v0/disability_compensation_in_progress_forms_controller.rb (+5/-5)

  • app/models/form_profiles/va_526ez.rb (+3/-2)

  • config/settings.yml (+7/-0)

  • config/settings/test.yml (+7/-0)

  • lib/disability_compensation/factories/api_provider_factory.rb (+11/-3)

  • lib/disability_compensation/providers/rated_disabilities/lighthouse_rated_disabilities_provider.rb (+35/-3)

  • lib/lighthouse/auth/client_credentials/service.rb (+4/-4)

  • lib/lighthouse/veteran_verification/configuration.rb (+96/-0)

  • lib/lighthouse/veteran_verification/service.rb (+21/-0)

  • lib/lighthouse/veteran_verification/service_exception.rb (+28/-0)

  • spec/lib/disability_compensation/factories/api_provider_factory_spec.rb (+14/-6)

  • spec/lib/disability_compensation/providers/lighthouse_rated_disabilities_provider_spec.rb (+1/-7)

  • spec/lib/lighthouse/veteran_verification/service_spec.rb (+30/-0)

  • spec/models/form_profile_spec.rb (+7/-0)

  • spec/requests/disability_compensation_form_request_spec.rb (+21/-1)

  • spec/requests/v0/disability_compensation_in_progress_forms_controller_request_spec.rb (+2/-0)

    Note: We exclude files matching the following when considering PR size:

    *.csv, *.json, *.tsv, *.txt, Gemfile.lock, app/swagger, modules/mobile/docs, spec/fixtures/, spec/support/vcr_cassettes/, modules/mobile/spec/support/vcr_cassettes/, db/seeds, modules/vaos/app/docs, modules/meb_api/app/docs, modules/appeals_api/app/swagger/
    

Big PRs are difficult to review, often become stale, and cause delays.

Generated by 🚫 Danger

@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main March 23, 2023 23:21 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 3, 2023 18:14 In progress
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 3, 2023 21:08 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 3, 2023 21:09 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 3, 2023 22:13 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 3, 2023 22:14 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 3, 2023 23:08 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 3, 2023 23:09 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 3, 2023 23:32 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 3, 2023 23:34 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 4, 2023 00:13 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 4, 2023 00:13 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 4, 2023 20:48 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 4, 2023 20:48 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 4, 2023 21:19 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 4, 2023 22:33 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 4, 2023 23:10 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 4, 2023 23:10 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 6, 2023 17:38 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 6, 2023 17:39 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 6, 2023 23:49 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 6, 2023 23:53 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 7, 2023 17:49 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 7, 2023 18:09 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 7, 2023 18:09 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 12, 2023 16:12 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 12, 2023 16:13 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 12, 2023 20:26 In progress
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 12, 2023 20:29 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 12, 2023 20:32 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 12, 2023 22:11 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 12, 2023 22:12 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 12, 2023 22:17 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 12, 2023 22:18 Inactive
@va-vsp-bot va-vsp-bot requested a deployment to master/main/bdex/54161 April 12, 2023 23:11 In progress
@aurora-a-k-a-lightning aurora-a-k-a-lightning marked this pull request as ready for review April 12, 2023 23:20
@aurora-a-k-a-lightning aurora-a-k-a-lightning requested review from a team as code owners April 12, 2023 23:20
@va-vfs-bot va-vfs-bot temporarily deployed to bdex/54161/main/main April 12, 2023 23:27 Inactive
@christinec-fftc
Copy link
Contributor

The team had a pairing session where we walked through this pr together. lgtm!

Copy link
Contributor

@mchae-nava mchae-nava left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took a pass clicking through, LGTM! Minor considerations, more for future thought

  • Minor comments/checks on tests
  • If I remember, there was a lot of discussion on the ticket tracking this work, and some shifts on how we approached this. Might be good to include a light context in the PR description, as well as any steps planned in the near future following this work


Flipper.disable(ApiProviderFactory::FEATURE_TOGGLE_RATED_DISABILITIES)
provider = ApiProviderFactory.rated_disabilities_service_provider(current_user)
expect(provider.class).to equal(EvssRatedDisabilitiesProvider)
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just marking here to note the comment I made yesterday about testing coverage, and that this could be made more robust by making sure the incorrect provider is not active, especially if the check is for a behavior

Copy link
Contributor

@ryan-mcneil ryan-mcneil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the additional reviews! 🚀

@aurora-a-k-a-lightning aurora-a-k-a-lightning merged commit 63cfaf0 into master Apr 14, 2023
@aurora-a-k-a-lightning aurora-a-k-a-lightning deleted the bdex/54161 branch April 14, 2023 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate eVSS calls to rated disabilities functionality (vets-api /rated_disabilities)
7 participants