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

API-42930-vnp-proc-service-2-standardization #19893

Closed

Conversation

stiehlrod
Copy link
Contributor

@stiehlrod stiehlrod commented Dec 13, 2024

Summary

  • Removes extra methods in definitions file, rename service, and removes extra tests.

Related issue(s)

Testing done

  • post '/:veteranId/power-of-attorney-request', to: 'request#create'
  • post '/:veteranId/power-of-attorney-request' in staging & check DD for wsdl call

What areas of the site does it impact?

modified:   modules/claims_api/app/clients/claims_api/bgs_client/definitions.rb
modified:   modules/claims_api/spec/lib/claims_api/find_definition_spec.rb

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 (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

@stiehlrod stiehlrod self-assigned this Dec 13, 2024
@stiehlrod stiehlrod requested a review from a team as a code owner December 13, 2024 18:01
@va-vfs-bot va-vfs-bot temporarily deployed to API-42930-vnp-proc-service-2-standardization/main/main December 13, 2024 18:19 Inactive
@stiehlrod stiehlrod marked this pull request as draft December 16, 2024 16:32
@va-vfs-bot va-vfs-bot temporarily deployed to API-42930-vnp-proc-service-2-standardization/main/main December 17, 2024 20:43 Inactive
@stiehlrod stiehlrod marked this pull request as ready for review December 17, 2024 20:47
@va-vfs-bot va-vfs-bot temporarily deployed to API-42930-vnp-proc-service-2-standardization/main/main December 17, 2024 21:02 Inactive
@@ -433,7 +433,7 @@ module VnpProcFormCreate
module VnpProcWebServiceBeanV2
DEFINITION =
Bean.new(
path: 'VnpProcWebServiceBeanV2',
path: 'VnpProcWebServiceBeanV2/VnpProcServiceV2',
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we adding the service to the path here? The other modules only have the Bean in the path. Is this pattern unique to 'Vnp' services?

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah, this is actually causing it to call for the WSDL.

Copy link
Contributor

@tycol7 tycol7 Dec 19, 2024

Choose a reason for hiding this comment

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

Sounds good! My mistake, I think this comment ☝️ means we want to remove the extra VnpProcServiceV2.

Comment on lines -214 to -224
context 'VnpProcWebServiceBeanV2' do
let(:endpoint) { 'VnpProcWebServiceBeanV2/VnpProcServiceV2' }

it 'response with the correct namespace' do
result = subject.for_service(endpoint)
parsed_result = JSON.parse(result.to_json)
expect(parsed_result['bean']['path']).to eq 'VnpProcWebServiceBeanV2'
expect(parsed_result['path']).to eq 'VnpProcServiceV2'
expect(parsed_result['bean']['namespaces']['target']).to eq 'http://procService.services.v2.vonapp.vba.va.gov/'
end
end
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we keep this test?

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.

4 participants