-
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
[home/sampleData] add empty migrationVersion to auto-migration objects #29226
[home/sampleData] add empty migrationVersion to auto-migration objects #29226
Conversation
Pinging @elastic/kibana-app |
What about Sample data saved objects from Canvas and GIS? Should those be updated as well? https://github.com/elastic/kibana/blob/master/x-pack/plugins/canvas/init.js#L10 https://github.com/elastic/kibana/blob/master/x-pack/plugins/gis/index.js#L63 |
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.
lgtm
code review, tested by loaded sample data saved objects and cycling kibana server to run migrations. No errors in kibana log.
💚 Build Succeeded |
elastic#29226) The sample data does not currently specify a migration version, which means we have manually update the data sets when updating the saved objects API. This just sets the migration version for all the saved objects to `{}`, which signals to the saved objects API that the object has not been migrated and should have all migrations applied.
💚 Build Succeeded |
#29226) (#29230) The sample data does not currently specify a migration version, which means we have manually update the data sets when updating the saved objects API. This just sets the migration version for all the saved objects to `{}`, which signals to the saved objects API that the object has not been migrated and should have all migrations applied.
6.x/6.7: 173dadc |
FWIW, I did try this in Canvas, and all the sample workpads worked fine. I also tried it with an existing instance, and everything worked as expected. |
The sample data does not currently specify a migration version, which means we have manually update the data sets when updating the saved objects API. This just sets the migration version for all the saved objects to
{}
, which signals to the saved objects API that the object has not been migrated and should have all migrations applied.