fix(grafana): use relative dashboard path (backport #874) #876
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.
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
git commit -S -m "YOUR_COMMIT_MESSAGE"
Related to #726
Description of the change:
Sets the
GRAFANA_DASHBOARD_EXT_URL
to the simple relative/grafana/
path, rather than the full Route URL.Motivation for the change:
Since Grafana and Cryostat are now deployed together behind a common auth proxy instance, the client accesses Grafana simply by navigating to
/grafana/
on the Cryostat UI URL. This change simplifies the setup so that there are now no more references to the full Route URL in the Deployment, so it is overall more dynamic and flexible. This will support cases where the user wishes to deploy Cryostat on a custom domain or custom subpath.This is an automatic backport of pull request #874 done by [Mergify](https://mergify.com).