Reporting: add a "Remove" action in "Reporting" Management app

[fbaligand]

Currently, when we go to "Management" app, and then to "Reporting" section, in the reports list, we don't have a "remove" button in "Actions" column.
This is quite annoying, when you generate a report (CSV, PDF), download it, and want to remove it immediately, because report is not useful anymore.

This would be great to add a "Remove" action available in reports list section.

[tsullivan]

@stacey-gammon do you know if there was ever a reason we didn't just add this?

Only reason I can think of to not do it, is the user privileges are likely read-only for the .reporting index.

A workaround is to use something like Curator to clean up old data. Curator is for deleting entire indices, though, and it doesn't know if the generated reports have been downloaded. That suggestion is probably more to address really, really old reports.

[fbaligand]

Yes, there is curator, and planned in 6.6, there will be Elasticsearch Index Lifecycle Management API that will allow to remove a full index automatically.
But this issue is not about removing a full (and old) index, but just one report.
It would be very helpful!

[stacey-gammon]

@tsullivan - the only reason I delayed implementing is that I really wanted reporting to use the saved object client interface, and use that to delete the documents. This would get us all the auth stuff for free, and the @elastic/kibana-security team really wants everyone to go through that interfaces. Also then we could use index migrations on the reporting index.

The task manager is coming soon too, and so there was an open question of where these task results would be stored - in the task manager, or still in the separate .reporting index? We decided to still keep the reports in the .reporting index because of risk of bloating the task manager, but it was also an open question at the time.

So, given all these things in flux, it felt like it'd be a hack to throw it in now. That being said, maybe it's worth a hack just to get it in there sooner. 🤔

[fbaligand]

Well, if migration to saved objects is planned for 6.6 release, then this fix is useless.
But if it is planned for 6.7 or even 7.0, then I think it is a quick win very useful!
Especially since there is currently no way to remove reports from Kibana UI.

[tsullivan]

@stacey-gammon totally agree on using the saved objects API. My understanding is that would do the work for us to ensure a user could only delete their own report job documents.

About the Task Manager topic, I replied over here: #23632 (comment)

[fbaligand]

Is there a pending PR "migrate Reporting section to Saved Objects" ?

[tsullivan]

@fbaligand no PR up yet. The details are in this issue: #21689

[fbaligand]

This feature seems to not be planned for Kibana 6.6. No ?
So the “remove” button in “Reporting” section may be relevant, waiting this feature being released.

[lexdevelop]

Still no action on this :(

[douniwan5788]

Need this !

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[iamhowardtheduck]

This has a been a major ask of a customer of mine. The usage of DevTools to delete reports over-complicates what should be a rather simple task.

Need this!