You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@guerler and I are on the same page that it would be awesome if you could publish a report to a page. I wanted to create an issue just to outline the backend because that is important to me.
I think it should maybe be:
/api/invocations/<id>/report/publish
I'd like it to go through the backend instead of through the client so we can leverage the functionality outside the webui (i.e. from future post workflow actions for instance or CLI pipelines). The backend also has functionality that will turn the invocation referenced objects into objects referenced by database ID which is what the pages need - so I think that will work better than translating them to encoded IDs and rewriting the page from those (although that should also work fine I suppose).
The text was updated successfully, but these errors were encountered:
@guerler and I are on the same page that it would be awesome if you could publish a report to a page. I wanted to create an issue just to outline the backend because that is important to me.
I think it should maybe be:
I'd like it to go through the backend instead of through the client so we can leverage the functionality outside the webui (i.e. from future post workflow actions for instance or CLI pipelines). The backend also has functionality that will turn the invocation referenced objects into objects referenced by database ID which is what the pages need - so I think that will work better than translating them to encoded IDs and rewriting the page from those (although that should also work fine I suppose).
The text was updated successfully, but these errors were encountered: