Conditional report actions

[TheSyscall]

Only show actions if there is actually an exporter for it.

Draft for now because of an issue that prevents PrintableHtmlDocument to be moved to icingaweb Icinga/icingaweb2#5510

• Remove PDF download option and mail attachment type when there is no pdfexport hook implementation registered
• Remove download dropdown and send button entirely if no export option is available

This serves as a step toward getting rid of pdfexport as a requirement for reporting, but does not get rid of this dependency entirely.

This combined with the changes made in #275 should allow us to remove pdfexport as a requirement. It is still not possible to use any module that implements the Pdfexport hook but at least the module is able to show reports in the web app and export to CSV and JSON.

• requires Add a hasLinks method to Dropdown ipl-web#367
• requires Remove dependency on pdfexport module for PDF export icingaweb2#5510
• relates to Switch back to using syncronous pdf export #275

[flourish86]

I'm not sure about the whole context.

But have you considered just disabling the non-available actions and including a tool tip that clarifies the reason, e.g. "PDF-Export not configured"?

My assumption is users might be looking for certain actions and wonder why they suddenly disappear or just expect certain options, as they're available in other modules.

Here are a few questions, that are important for deciding, what the better option would be.

• Are the actions unavailable temporary or permanently in the Icinga Web 2 instance, so users never expect them to be there?
• Is there a way to solve it for regular users or does the Admin have to do it.

[TheSyscall]

My assumption is users might be looking for certain actions and wonder why they suddenly disappear or just expect certain options, as they're available in other modules.

This PR just mimics the behavior of icingaweb itself, which hides the download as PDF button from the tab bar under similar conditions.

Are the actions unavailable temporary or permanently in the Icinga Web 2 instance, so users never expect them to be there?

There is no way to know that, the reason the PDF export button is not available is always the same though, there is no hook implementing the PdfExportHook. That might be because there is an issue with the hook implementation, or the hook failed to register, the admin disabled it, or it was never active in the first place.

Is there a way to solve it for regular users or does the Admin have to do it.

It is always on the admin to solve this.