Closed WadeBarnes closed 6 months ago
OrgBook monitoring also needed to be updated. Not so much of an issue as the monitoring should use a specific API, but it does help to indicate the breadth of the impact of the change.
Seems like the call to /quickload
is failing because of the redirect. Might need to amend the API to add it as a /v4 endpoint or call /v2
directly in the web app
I don't believe anything else relies on /v2
by default so updating the web app will be the easiest fix
/api/quickload
is not the only API call being affected.
I'm sure there are others.
After deploying the latest updates to both Aries-VCR and the OrgBook-BC-Client, the OrgBook is broken. There are likely other issues, and they are likely all related to the update to the API which redirects to API
/v4
by default, but here are two to start.Issue 1
Steps to reproduce:
test
TEST COOP TEST
Result:
Expected Result:
Issue 2
Steps to reproduce:
Result:
Expected Result: