Fix legacy requests for /heath/info page #860
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://eaflood.atlassian.net/browse/WATER-4375
Recently we extended the functionality of our code that manages sending requests to the legacy services to Add defra-user-id header to legacy requests. This is in preparation for us managing the setup bill run process as part of changes we're doing to support two-part tariff. Some of the legacy endpoints expect the header and use it to authorize the request being made.
When we did this we overlooked the requests being made in
app/services/health/info.service.js
. The calls it was making told our logic to send the requests to the base domains for each legacy service, for example,http://localhost:8001
. But because of the new param and a change in their order, this was being received as the user ID arg. So, we broke a number of the requests. 🤦This change fixes the requests being made in
InfoService
.