Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix legacy requests for /heath/info page #860

Merged
merged 4 commits into from
Mar 26, 2024
Merged

Conversation

Cruikshanks
Copy link
Member

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.

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](#796). This is in preparation of 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`.
@Cruikshanks Cruikshanks added the bug Something isn't working label Mar 26, 2024
@Cruikshanks Cruikshanks self-assigned this Mar 26, 2024
@Cruikshanks Cruikshanks marked this pull request as ready for review March 26, 2024 16:00
Copy link
Contributor

@rvsiyad rvsiyad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Cruikshanks Cruikshanks merged commit 501e812 into main Mar 26, 2024
6 checks passed
@Cruikshanks Cruikshanks deleted the fix-health-info-page branch March 26, 2024 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants