-
Notifications
You must be signed in to change notification settings - Fork 303
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
Support Grafana 5.0 API changes #28
Comments
Nope, sorry. I have not checked yet. A PR would be welcome. I wonder what would be the best approach to handle such a breaking change? One could release a new version that only works with 5.0 and have the old version work with pre 5.0 grafana. Or it could support both via a grafana-version flag... |
Does not work fully. The PNGs seem to be downloaded, but are not displayed in the generated PDF. |
I just downloaded grafana 5.0 and tested against the latest master of grafana-reporter. Everything seems to work fine. Closing this issue until I get some concrete examples to the opposite. |
Hmm from the docs I see:
Will see if I can support the new API, to avoid nasty surprises in a future release when the deprectation happens. |
Not the greatest workaround, but I didn't have time to look for a better working solution at the moment. I personally left in the original for backwards compatibility. Regardless, it does look like rows are being fazed out.
|
Yes and this type of solution for supporting both seems to be required, since old imported dashboards still return rows when fetched via the new API Grafana 5. |
Necessary for #28. New version JSON doesn't have rows, instead panels have moved to the top level. We still need to support the old version seamlessly, since even a v5 grafana can return the old structure. Presumably this grafana behaviour is to support backwards compatibility. It seems old dashboards still return the old structrue, while new dashboards greated with Grafana 5 return the new structure.
Partially addresses #28. Still support Grafana v4 via existing reporter API. Add new API to use with Grafana v5.
Necessary for #28. New version JSON doesn't have rows, instead panels have moved to the top level. We still need to support the old version seamlessly, since even a v5 grafana can return the old structure. Presumably this grafana behaviour is to support backwards compatibility. It seems old dashboards still return the old structrue, while new dashboards greated with Grafana 5 return the new structure.
Necessary for #28. New version JSON doesn't have rows, instead panels have moved to the top level. We still need to support the old version seamlessly, since even a v5 grafana can return the old structure. Presumably this grafana behaviour is to support backwards compatibility. It seems old dashboards still return the old structrue, while new dashboards greated with Grafana 5 return the new structure.
I missed this bug (was introduced in a recent PR). Luckily it seems harmless. Fixed it now while making the other changes. |
The v2.0.0 release addresses this issue. |
Has this been tested against the 5.0 rework? As i know the dashboard permalinks have been changed etc. I'm gonna prep a box to test it but was wondering if the devs have checked it for compatability yet?
The text was updated successfully, but these errors were encountered: