This repository was archived by the owner on Sep 30, 2024. It is now read-only.
migration: Return leaves when stitching definitions#39459
Merged
Conversation
This was referenced Jul 26, 2022
1703638 to
334c872
Compare
334c872 to
5529263
Compare
chrismwendt
approved these changes
Jul 26, 2022
Co-authored-by: Chris Wendt <chrismwendt@gmail.com>
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This PR returns additional data when stitching together migration definitions over multiple releases. We also need to know in the migration graph where we can "pause" to ensure that out of band migrations have run prior to upgrading the schema into a future state that is no longer compatible.
Test plan
Existing and new unit tests.