-
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
Fix importing dashboards created before ~6.1.0 #94332
Conversation
Pinging @elastic/kibana-presentation (Team:Presentation) |
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.
Skipping extractReferences
for panels older than 7.3.0 makes a lot of sense.
All the tests here look great! Thanks again for tackling this Anton.
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.
I'm just curious about the exports location. Both archivers (kbnarchiver & esarchiver) have locations that are documented. Should this be similar?
await PageObjects.settings.navigateTo(); | ||
await PageObjects.settings.clickKibanaSavedObjects(); | ||
await PageObjects.savedObjects.importFile( | ||
path.join(__dirname, 'exports', 'dashboard_6_0_1.json') |
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.
Is this a common location for an export?
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.
TBH, I am not sure what is the best practice. I followed another example I found where saved object import was used:
https://github.com/elastic/kibana/blob/master/test/functional/apps/management/exports/mgmt_import_objects.json
LGTM pulled it down and tested it. Will be testing it again in the next 7.12 BC. Thanks @Dosant |
@elasticmachine merge upstream |
870dfd9
to
1452b69
Compare
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Summary
Fixes #93772
Regression introduced in #82602
How to test
Before fix:
No panels on a dashboard. Client-side error.
**After the fix: **
The panel is shown and ideally working (unless there is some other unrelated migration issue because of the visualization/indexpattern)
Fix details
More context is here: #93772,
but the fix, in a nutshell, is to skip an
extractReferences
code path which we know is supported only for >7.3.0 panels.Release Notes
Fixed importing dashboards created before 6.1.0 version
Checklist
For maintainers