EVSS PCIU Migration: Step 6: Monitor Betamocks setup

[RachalCassity]

Test Plan: Step 5 Remove PCIU

Summary

Per the meeting on 8/19, the Platform Product team will not be doing the work on this, that will be done by Authenticated Experience team. The Platform Product team will be monitoring the work.
VAProfile Betamocks examples have not been recorded. Follow these instructions to record the VAProfile::ContactInformation response.

Tasks

• Monitor the Authenticated Experience team while the tasks are executed
• Add VAProfile to make_table.rb
• Record VAProfile::ContactInformation::Email response and push changes to the Vets-API mockdata
• Add VAProfile::ContactInformation to VetsAPI Betamocks Setup:

# VAProfile::ContactInformation
- :base_uri: <%= "#{URI(Settings.vet360.url).host}:#{URI(Settings.vet360.url).port}" %>
  :endpoints:
  - :method: :get
    :path: "/demographics/demographics/v1/*/*"
    :file_path: "vet360/demographics/default"

• Update doc: Betamocks Mockdata Example
• Review all Betamocks documentation and instructions

Related issues

VA Profile Mockdata can completed concurrently with this ticket.

[RachalCassity]

Reached out to Auth Exp for help in this slack thread

[jennb33]

This ticket may be split and the remaining work will go into the next Sprint.

[RachalCassity]

@jennb33 This ticket should be moved to the next sprint. This work mirrors VA Profile Mockdata solution ticket and can be done concurrently.

Update mockdata instructions will also be added as a task.

[LindseySaari]

Here is a doc that provides steps for creating a Ruby script to record responses from the VA Pro Contact Info API.

There are two more docs to assist in recording responses:

• Authenticated Experience: Using Mock Data - outlines some steps for setting up a local env with mock data.
• Profile: Mocking Data for VA Profile Service History API - outlines steps for connecting local vets-api to staging APIs and recording mocks.

[RachalCassity]

Setup a remote branch in the vets-api. Waiting for the meeting with VA Profile to answer questions.

[RachalCassity]

This may have to be post-poned until the VAProfile version update has been completed. VAProfile V3 needs different credentials and might have different outputs.

[jennb33]

8/5 update: this needs to be reviewed for assignment to other VFS team.

[rmtolmach]

@jennb33 in the meeting notes from yesterday, it was decided our team won't do this work but we'll pass it to the owning team.

[jennb33]

Thanks, @rmtolmach - I've updated the name and summary for this ticket to be more focused on the monitoring of the work

[jennb33]

10/10/2024: @rjohnson2011 has been researching the information to update the ticket. Documentation is clear. Will reach out in Slack if there are any issues.

[rjohnson2011]

Spoke with Tom Harrison (PM of Authenticated Experience) regarding this ticket. There is an initiative in place to replace Betamocks with an internal tool to record mock data in an upcoming sprint led by Charley Stran. We agreed it would be redundant and unnecessary to record these mock calls twice.

Relayed this into to Lindsey H and she also agreed this ticket is no longer relevant due to the upcoming internal tool to record mock calls.