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
Report data (GTL) API for with pagination, filtering and more #14924
Comments
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
@martinpovolny is this still a valid issue. If not can you close. |
Yes it is, as far as I know, no progress has been made yet in exposing all those Cc @kbrock you mentioned having an idea about some "ruport lite" that would expose those over the API? |
I thought we had a report data endpoint. But possibly not. Yea. I haven't done anything here |
Yes, this still is an issue. I am not aware of any effort on the API side that would adress this. Although on the UI side this is already handled by a component that could consume some API if such was available. |
@abellotti @gtanzillo would the API repository be a better place for this issue? |
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
Since ManageIQ/manageiq-ui-classic#592 the OPS UI is consuming report data served by a JSON endpoint to present the GTL (Grid, table, list) views.
A significant part of all the transactions in the OPS UI goes through this path so this is an opportunity to move forward with the usage of the API in the OPS UI.
We need an API endpoint so that the GTL component would consume the API rather than the current JSON endpoint implemented in the OPS UI controller code.
Ping @chessbyte : this is what we where discussion on various ocasions. Ping @abellotti, @jntullo.
Please, take a look, let's get this moving forward.
Ping @himdel, @karelhala, @mtho11
The text was updated successfully, but these errors were encountered: