-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow movement of DMS tasks to new instances #30721
Allow movement of DMS tasks to new instances #30721
Conversation
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @misterjacko 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
new test added and passed:
|
Hi @justinretzolk ! Anything holding this up that I could address? Thanks for reviewing! |
Hey @misterjacko 👋 Thank you for taking the time to raise this, and for checking in on it! On a quick glance, everything looks to be in good shape for review. Unfortunately I can't provide an ETA on when this will be reviewed/merged due to the potential of shifting priorities. We prioritize by count of 👍 reactions and a few other things (more information on our prioritization guide if you're interested). |
@misterjacko Thanks for the contribution 🎉 👏. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This change enables movement of DMS Tasks between DMS Instances in place rather than destroy and recreate by leveraging the MoveReplicatonTask operation.
Tests were also fixed so that they pass.
In addition, as mentioned in #29765 the 5 minute timeout for certain other actions is often not sufficient for how long DMS takes. While this PR does not address making those timeouts user configurable, it does increase that timeout and should reduce failures.
Relations
Closes #30709
Closes #29765
References
Output from Acceptance Testing
New tests: #30721 (comment)