feat: update panels that used deprecated angular plugins #456
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Timo Hankamer <[email protected]>
tibuntu
force-pushed
the
replace-angular-grafana-plugins
branch
from
6875f4b
to
a3f4e3e
Compare
|
thanks a lot for your support and effort, I will test them locally as well. You can ignore the linting error, I will bump versions when I prepare the release. |
Pull Request Test Coverage Report for Build 9609416737Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi there,
Grafana has announced that some plugins that used angular (E.g.
graph) are going to be deprecated.With the new Grafana 11 release, panels using these plugins will not longer work.
See: https://grafana.com/docs/grafana/latest/breaking-changes/breaking-changes-v11-0/#angularjs-support-is-turned-off-by-default
Since we are using Kyverno + Kyverno-Policy-Reporter we would like to update the affected dashboards prior to upgrading Grafana.
I know that it's really hard to properly review the JSON diff. I was able to render all dashboards (ConfigMaps) and was also able to import them into Grafana without any issues.
Let me know if you need more details/infos.
Thanks!