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.

Sign up for GitHub

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

Jump to bottom

Remove v1 saved object migrations #91619

Closed
rudolf opened this issue Feb 17, 2021 · 1 comment
Closed

Remove v1 saved object migrations #91619

rudolf opened this issue Feb 17, 2021 · 1 comment
Labels
Feature:Saved Objects project:ResilientSavedObjectMigrations Reduce Kibana upgrade failures by making saved object migrations more resilient

Comments

@rudolf
Copy link
Contributor

rudolf commented Feb 17, 2021

When we introduce v2 saved object migrations (#78413, #89297) we kept the v1 migrations with the migrations.enableV2 configuration option to switch between the two. This is a failsafe mechanism so that if we discover a bug in the v2 migrations there is a way for users to quickly get their upgrades working again.

Keeping both migration algorithms introduced some technical debt, so we should ideally remove this code as soon as we have confidence in the new migration algorithm.
@rudolf rudolf added Feature:Saved Objects project:ResilientSavedObjectMigrations Reduce Kibana upgrade failures by making saved object migrations more resilient labels Feb 17, 2021
@pgayvallet pgayvallet mentioned this issue Jun 8, 2021
Open
17 tasks
@pgayvallet pgayvallet mentioned this issue Jul 1, 2021
Open
@joshdover
Copy link
Contributor

Duplicate of #96396

@joshdover joshdover marked this as a duplicate of #96396 Jul 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Saved Objects project:ResilientSavedObjectMigrations Reduce Kibana upgrade failures by making saved object migrations more resilient
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rudolf @joshdover