fix: don't use dashboard cache if url is different #841
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
Currently, dashboard cache is still being used even if URL changes. The PR addresses that.
Other changes:
*metav1.Duration
tometav1.Duration
where the former was not really needed (GrafanaDashboardStatus
,GrafanaSpec
);NewDashboardPipeline
would fallback to 24h instead of 0(=infinity) ifdashboard.Spec.ContentCacheDuration
is not defined. Removed that;obtainJson()
toloadDashboardFromURL()
. - I think that location makes more sense.Type of change
Checklist
Verification steps
PR
I think tests should already offer a comprehensive picture.
Extra notes
Ideally, we should have an automated e2e-test for testing the caching mechanism. For now, something like this would work:
Depending on the settings, you should start seeing records in the access log.
Options:
contentCacheDuration: 20s
inGrafanaDashboard
spec;dashboardContentCacheDuration: 1m
inGrafana
spec;