PPMS: Verify updated Production endpoint API / key

[jilladams]

Prerequisites

• Recruit Devops help for potential weekend work, if not possible to complete ON Fri Aug 2
  • Verify where / how we can test the Prod key. Will Staging use the key?
• Receive API key / URL from PPMS

User Story or Problem Statement

Original thread from PPMS nprod update: https://dsva.slack.com/archives/C0FQSS30V/p1715982323485409 (#18205) Timeline for PPMS prod update: https://dsva.slack.com/archives/C03LFSPGV16/p1719940170217209

PPMS is updating Prod API keys and URL that should be used for API calls. Platform Devops manages API keys for us in AWS param store, AND where the vets-api forward proxy port points to, for those calls.

Announcement:

BLUF: Provider Profile Management System (PPMS) will be migrating it's Azure Environments to a dedicated Azure Subscription. Included in the subscription migration, PPMS will also be upgrading to the Azure Services Environment (ASE) version 3. INT/PPD will begin Testing May 20, 2024 through May 24, 2024. A new URL and the API Subscription Key for your product will be sent this week before testing begins. Please update your new key on 05/20/2024. BACKGROUND: VAEC informed PPMS that Azure will be deprecating Azure Services Environment (ASE) version 1 & 2 on August 31, 2024. PPMS has taken advantage of this opportunity to upgrade the current ASE v.2, which requires a migration from our current Shared Subscription to a Dedicated Subscription. These improvements will enhance performance/ scalability, simplify management, and aide in futureproofing for ongoing improvements. Next Steps:

• [ ] Obtain new Prod subscription key from PPMS Team (before August 2)
• [ ] Request that Devops update the Key in the AWS parameter store (on August 2)
• [ ] Request that Devops also update the URL used for the forward-proxy to reach PPMS (on August 2)
• [ ] By Sunday August 4: Verify on va.gov (using ArgoCD?) that Facility Locator is able to:
  • [ ] Return typeahead suggestions for Service when Facility Type is Community Care provider, or Community Care pharmacy
  • [ ] Return Community care providers
  • [ ] Return Community care pharmacies

Acceptance Criteria

• [ ] Facility Locator can return PPMS data (community care) successfully after API key / URL update

[jilladams]

Re: testing from Eli: For the prod key we cannot verify on dev.va.gov (bc dev uses its own PPMS key for nprod env.)

We need to figure out where we can test:

• Prod only?
• Could we test on Staging? This would require the ability to change the Staging forward proxy destination independent of prod. Devops will need to tell us. If so, we could:
  • Have Devops put API key in the AWS param store
  • Have Devops update Staging Fwdproxy
  • Test/ verify on Staging
  • Have Devops update Prod (and verify)

If Staging points to Dev, we will have to test on prod, and roll back if it fails.

[jilladams]

Started a thread with Devops in the COP channel to see about securing resources over the weekend of 8/2-4: https://dsva.slack.com/archives/C04CYC4LMU6/p1720040117841219