Check base url injected into the client via global config object #1198
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.
Description
The base url of the check service, was previously injected into the frontend via an env variable (WANDA_URL), populated at build time.
This behavior leads to a bug where the user cannot add the base url of the check service because that can be only set at assets build time, when we build the image basically. We need to give the user the ability to specify on which path/url is present the check service in their infrastructure. This can be a path "/check_service" or a full url like we can see on the development configuration.
This configuration is then used by axios to compose the base url of the checks frontend library.
This is similar to grafana public url handling.
Jest configuration updated to perform tests with the global config.
The helm chart needs to be updated.
How was this tested?
Automated tests