Add comprehensive AAP instance migration playbook #217
Conversation
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
This commit adds a complete solution for migrating all resources from one AAP instance to another, including: - migrate_aap_instance.yml: Main migration playbook that orchestrates the full export, import, and validation process across three phases - migration_vars.yml.example: Example configuration file with all available options, including vault encryption examples and multiple use cases - MIGRATION_GUIDE.md: Comprehensive 600+ line documentation covering: * Quick start guide and prerequisites * Detailed phase-by-phase migration process * All configuration options with examples * Best practices for before, during, and after migration * Troubleshooting common issues * Advanced scenarios (multi-stage, cross-version, selective resource) - Updated README.md with migration section linking to the guide The migration playbook supports: - 46+ AAP resource types (Controller, EDA, Gateway) - Full or partial migrations (by organization or resource) - Post-migration validation and drift detection - Ansible Vault for credential security - Structured or flattened export formats - Optional cleanup of unmanaged resources This leverages existing collection roles (filetree_create, filetree_read, object_diff, dispatch) to provide a turnkey migration solution.
ivarmu
requested changes
Jan 7, 2026
Contributor
ivarmu
left a comment
ivarmu
left a comment
There was a problem hiding this comment.
Great! LGTM. Just fix the two errors reported by the CI.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 commit adds a complete solution for migrating all resources from one AAP instance to another, including:
migrate_aap_instance.yml: Main migration playbook that orchestrates the full export, import, and validation process across three phases
migration_vars.yml.example: Example configuration file with all available options, including vault encryption examples and multiple use cases
MIGRATION_GUIDE.md: Comprehensive 600+ line documentation covering:
Updated README.md with migration section linking to the guide
The migration playbook supports:
This leverages existing collection roles (filetree_create, filetree_read, object_diff, dispatch) to provide a turnkey migration solution.
What does this PR do?
How should this be tested?
Is there a relevant Issue open for this?
resolves #[number]
Other Relevant info, PRs, etc