Skip to content
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] Fix missing force now behaviour for v2 reports #114516

Merged
merged 4 commits into from
Oct 12, 2021

Conversation

jloleysens
Copy link
Contributor

Summary

Fix #114193

Adds the forceNow parameter to the reporting's redirect app which fixes potential time drift issues.

Also removes the forceNow parameters from locators.

Checklist

@jloleysens jloleysens added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead v8.0.0 release_note:skip Skip the PR/issue when compiling release notes Team:Reporting Services v7.16.0 labels Oct 11, 2021
@jloleysens jloleysens requested a review from dokmic October 11, 2021 15:37
@jloleysens jloleysens requested review from a team as code owners October 11, 2021 15:37
@elasticmachine
Copy link
Contributor

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

@jloleysens
Copy link
Contributor Author

CC @tsullivan @vadimkibana @ppisljar

@jloleysens jloleysens changed the title fix missing force now behaviour for v2 reports Fix missing force now behaviour for v2 reports Oct 11, 2021
@jloleysens
Copy link
Contributor Author

@elasticmachine merge upstream

@jloleysens jloleysens changed the title Fix missing force now behaviour for v2 reports [Reporting] Fix missing force now behaviour for v2 reports Oct 12, 2021
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Copy link
Contributor

@dokmic dokmic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@jloleysens jloleysens merged commit afe81bb into elastic:master Oct 12, 2021
@jloleysens jloleysens deleted the reporting/fix-use-of-force-now branch October 12, 2021 13:49
jloleysens added a commit to jloleysens/kibana that referenced this pull request Oct 12, 2021
…14516)

* fix missing force now behaviour for v2 reports

* added jest test

* updated jest test snapshot to match removal of forceNow injection from locator params

Co-authored-by: Kibana Machine <[email protected]>
jloleysens added a commit that referenced this pull request Oct 12, 2021
…114634)

* fix missing force now behaviour for v2 reports

* added jest test

* updated jest test snapshot to match removal of forceNow injection from locator params

Co-authored-by: Kibana Machine <[email protected]>

Co-authored-by: Kibana Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead release_note:skip Skip the PR/issue when compiling release notes v7.16.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Reporting] V2 PDF and PNG reports have time drift when time filter uses relative time range.
4 participants