Closed nosovk closed 9 months ago
Hey, we put that here https://github.com/metabase/metabase/issues/35365, but seems that the long list of things we shipped swallowed it through.
You will need to call the collections endpoint, get the collections, then iterate over those and get the dashboards of each of those, and then get iterate on dashboards and get the details of each.
A sample of that approach can be seen here: https://github.com/paoliniluis/metagraph/blob/a1c87f38a48d457d35dc6341af0d82135b2a3d14/main.py#L257C44-L257C44
Hey, we put that here #35365, but seems that the long list of things we shipped swallowed it through.
You will need to call the collections endpoint, get the collections, then iterate over those and get the dashboards of each of those, and then get iterate on dashboards and get the details of each.
A sample of that approach can be seen here: https://github.com/paoliniluis/metagraph/blob/a1c87f38a48d457d35dc6341af0d82135b2a3d14/main.py#L257C44-L257C44
Hello, the removal of this endpoint has caused some issues in applications, plugins, and microservices that I manage, as well as in those of other developers I know. Was its removal really necessary?
this is breaking change, we hade some hard time to find out what was wrong, and currently mitigating issue by blocking update of our metabase instance. But I hope there will be some solution to get that functionality back to new version, because we can't use version that has no security updates....
Describe the bug
Prior to 0.47 version there was an api method get-apidashboard see docs but it's missing in 0.48 build.
There was no announcement of that api method removal
To Reproduce
Expected behavior
I expect to be able to use previously existing api, or at least some noification about api deprecation at least
Logs
No response
Information about your Metabase installation
Severity
blocking an upgrade
Additional context
No response