[Reporting] Guide users to the new CSV export type #102833
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Closes #100363
This change "nags" users to change a POST URL that was created in an older version of Kibana, by allowing an export to set a new field:
payload.isDeprecated
. This triggers logging and the UI to notify the user that the export type will not be supported in 8.0.Release notes
For CSV reports, using a POST URL copied from an older version of Kibana will result in a warning. A POST URL copied in Kibana 7.12 or lower will not be supported in 8.0. The POST URL should be regenerated in the latest version of Kibana for automation to continue seamlessly.
How to test
Testing requires copying a POST URL for CSV Export in Kibana 7.12, upgrading the instance to 7.x with this code change, and then send a POST request to the URL. Since the POST URL references a deprecated export type (
/generate/csv
), a warning gets logged in the Kibana server, and the job gets a warning treatment in the Reporting UI at Stack Management > Reporting.Steps to set up a POST URL of the deprecated export type and send it to a 7.x Kibana instance with these changes:
generate_deprecated_csv.sh
Checklist