Champva 94284 pega reporting api connection

[stevelong00]

Summary

• This work is behind a feature toggle (flipper): NO
• Created a client for the Pega API with some tests to make use of it.
• We will need to retrieve data from this API in upcoming tickets. With this ticket we have implemented a simple API client and some test code as a proof of concept.
• I work for the IVC Forms team and we own this module.

Related issue(s)

• The associated ticket

Testing done

• New code is covered by unit tests
• Prior to this change there was no client for the Pega API. With this change, there is a client that is only used by unit test code.
• In addition to running the test suite, verification can be performed by:
  • Enable the 'hit the production endpoint' test
  • Configure the API key in your local environment as described in the comments
  • Run this test locally
  • Verify the response using a debugger

Screenshots

None

What areas of the site does it impact?

None, this code is only used by unit tests so far.

Acceptance criteria

• I 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

Requested Feedback

None

[michaelclement]

@stevelong00 after troubleshooting with Cindy we found that the headers were automatically getting converted to have an uppercase first letter. Cindy updated her python lambda to grab the headers using appropriate casing and I was able to use your existing code to pull a report in the Argo staging console.

[michaelclement]

I think we want that prefill line in here (for when users have save-in-progress'd data).

[michaelclement]

Also, I've added the production API key to the AWS param store under this path.

[stevelong00]

Thanks! I wasn't sure if that prefill line was a placeholder or if it was doing something.

[michaelclement]

Looks great!

[michaelclement]

Not a blocker, but we may want to move this into our AWS param store at some point in the future.

[stevelong00]

I was thinking about that, but this is how paths are being stored elsewhere in similar code so I decided to err on the side of consistency.