feat(validate-migration): add post-migration checks#17
Conversation
|
This is okay as long as the goal was just to validate the configuration has value set. |
sabre1041
left a comment
There was a problem hiding this comment.
In addition to the comment regarding making prevalidation checks conditional, would you be able to rebase from main as there are corrections to variable names
@stevefulme1 still need a rebase here to pick up the upstream variables |
e274b03 to
1456003
Compare
sabre1041
left a comment
There was a problem hiding this comment.
Content looks good. Just need to resolve the tests failure
Add post-migration validation tasks to the existing validate_migration role covering VM configurations, data volumes, network attachments, and resource relationships. Validates migrated VirtualMachines have correct spec fields, DataVolumes are Succeeded, PVCs are Bound, networks match, and detects orphaned or missing DataVolumes. Resolves: MFG-423 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add validate_migration_pre_enabled boolean (default: true) to gate pre-migration infrastructure checks, matching the post-migration pattern per reviewer feedback.
1456003 to
9f71e5e
Compare
|
@sabre1041 Rebased on main, added pre-migration validation toggle ( |
|
Merging as failing slack notification is not part of this pr |
Summary
validate_migrationrole with post-migration validation tasks (gated behindvalidate_migration_post_enabled: true)playbooks/validate_migration.ymlplaybookResolves
MFG-423 — Migration Logic Validation and Testing
Usage
Test plan
yamllintpasses (confirmed locally)ansible-lint --offlinepasses production profile (confirmed — 0 failures)validate_migration_post_enabled: false(default)🤖 Generated with Claude Code