Welcome, PacificSource!

[trentonyo]

Fix PacificSource Endpoint

ASSOCIATED ISSUES:

• Resolves #54
• Closes #56
• PacificSource endpoint now passes all tests on home machine

Description

🥳 PacificSource Endpoint: We can now query PacificSource! Re-run the configMaker script (instructions here) to get the latest configuration, then boot up a query and see what PacificSource has to say about it!

🆕 HTTP Client mode: In order to facilitate the above, we now have a new method of sending queries. We use the lower-level alternative to requests in HTTP.client. This option has been propagated across the configuration maker so it can be applied to any endpoint, if that endpoint has certain qualities or needs!

✅ API Multiple Responses: Fixed issue #56 with a small patch, search for one of the providers in the #resource channel to see responses from more than one endpoint.

Definition of Done

• [x] Acceptance criteria are validated
• [x] Changes are approved
• [x] Contains no breaking changes
• [x] Changes are implemented in all components
• [x] Each component associated with issue is updated (no stubs)
• [x] Each new feature has unit tests written and confirmed
  • [x] The new feature "HTTP Client mode" is tested by integration testing the PacificSource endpoint
• [x] All tests pass, no regressions
• [x] All documentation is updated, including release notes

[trentonyo]

Addendum: Damn it.

The GitHub Actions worker still tries an SSL handshake, and turns out my laptop does too.

These fixes only pass on my desktop, and I would assume also Kevin's home computer. @kecarman74 , perhaps there's something common to your environment and my environment that we could specify in the HTTP.client request? It's definitely using HTTP 1.1, but maybe there's even more to it

[ImgyeongLee]

Nice insecure connection