Migration from aws-on-prem repo #90
Open
+154
−48
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
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on January 26. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issues Closed
Brief Summary
Adds support for migrating
aws-on-premrepo toenterprise.Detailed Summary
Adds
migrate-state.shbash script to handle the moving or renaming of Terraform state objects that can't be moved natively (e.g. after a submodule provider declaration was removed).Changes
Unrelated Changes
prepare.shscript to allow its execution from other directories (e.g.../../prepare.sh).Future Work
Archive the
aws-on-premproject once all environments have been migrated.Steps to Test
aws-on-preminstallationinfraandparagonworkspace following steps in its MIGRATE.mdenterpriseworkspaces apply without errorDeployment Notes
This migration should not be performed without Paragon oversight.