-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Reporting/Legacy] Remove reporting legacy job params compatibility shim #52539
[Reporting/Legacy] Remove reporting legacy job params compatibility shim #52539
Conversation
bf4fe08
to
e53d7b1
Compare
e53d7b1
to
005faf5
Compare
005faf5
to
d2cbb51
Compare
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
@elasticmachine merge upstream |
@stacey-gammon had asked about the validity of removing the compatibility layers in this PR. There are removed log lines where the previous code was warning when the reporting flow would go through the compatibility layers: So to make it clear, the behavior being removed has been getting logged as deprecated in previous versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+38 −724
APPROVED
Removed 7.6.0 label: Do not backport this breaking change to 7.x (may cause merge conflicts with future backports: sorry) |
@tsullivan Can you please add this change to the Breaking Changes in 8.0 doc? |
Sure: #56187 |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
test comment, ignore me |
Closes
Release note:
Kibana Reporting is no longer compatible with POST URL snippets that were generated with Kibana 6.2 and below. Please use Kibana UI to re-generate the POST URL strings if you depend on these for automated PDF reports.
Separate release note:
Fixed an issue in Reporting where the type of report would sometimes not appear in the job listing.