-
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
use kbnArchiver and test_user with minimal role in x-pack/test/functional/apps/rollup_job/tsvb.js #107712
Closed
+64
−4
Closed
use kbnArchiver and test_user with minimal role in x-pack/test/functional/apps/rollup_job/tsvb.js #107712
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
39 changes: 39 additions & 0 deletions
39
x-pack/test/functional/fixtures/kbn_archiver/rollup/rollup.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
{ | ||
"attributes": { | ||
"accessibility:disableAnimations": true, | ||
"buildNum": 9007199254740991, | ||
"dateFormat:tz": "UTC", | ||
"defaultIndex": "rollup", | ||
"visualization:visualize:legacyChartsLibrary": true, | ||
"visualization:visualize:legacyPieChartsLibrary": true | ||
}, | ||
"coreMigrationVersion": "7.15.0", | ||
"id": "7.15.0", | ||
"migrationVersion": { | ||
"config": "7.13.0" | ||
}, | ||
"references": [], | ||
"type": "config", | ||
"updated_at": "2021-08-04T23:35:47.992Z", | ||
"version": "WzQwLDFd" | ||
} | ||
|
||
{ | ||
"attributes": { | ||
"fieldAttrs": "{}", | ||
"fields": "[]", | ||
"runtimeFieldMap": "{}", | ||
"timeFieldName": "@timestamp.date_histogram.timestamp", | ||
"title": "rollup*", | ||
"typeMeta": "{}" | ||
}, | ||
"coreMigrationVersion": "7.15.0", | ||
"id": "rollup", | ||
"migrationVersion": { | ||
"index-pattern": "7.11.0" | ||
}, | ||
"references": [], | ||
"type": "index-pattern", | ||
"updated_at": "2021-08-04T23:22:14.902Z", | ||
"version": "WzIyLDFd" | ||
} |
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.
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.
Just out of curiosity, is this actually needed? It looks like you load a config object from
rollup.json
that already sets the default index to "rollup".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.
@jportner I just had a discussion with @wayneseymour about this for another test he's working on. I don't really understand why, but the "config" object we load from an archive never seems to be used. After this kbnArchive is loaded, if you look at the saved objects, you'll find another one for the current version and it won't have the defaultIndex set. I don't know if it's only because the version doesn't match, or if Kibana already created another one? It could be because we don't treat the previous version config object like an upgrade case on dev builds?
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.
Ah, interesting! Not sure why but it's good to know for future reference!