fix(e2e): check target migration via API dry run#2519
Merged
Conversation
hardcoretime
approved these changes
Jun 22, 2026
Isteb4k
approved these changes
Jun 22, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
Target migration precheck now validates the feature by creating a dry-run
VirtualMachineOperation, without readingModuleConfigfeature gates.Why do we need it, and what problem does it solve?
The precheck used
ModuleConfigas the source of truth, but it does not reliably reflect whether target migration is actually available. The API dry run checks the real behavior instead.What is the expected result?
Run target migration precheck: it should pass when the API accepts a target migration operation and fail when the operation is not supported.
Checklist