-
Notifications
You must be signed in to change notification settings - Fork 91
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
new: Add support for Unified Migrations #1150
new: Add support for Unified Migrations #1150
Conversation
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.
I get a 5xx error occasionally but other than that it looks good
2c06f69
to
994d489
Compare
Timeout occasionally happened during my tests. Is it possible to increase the time out value? Maybe change I also thought about change the timeout in runtime when the region change is detected but couldn't think about a way to implement it because the update function can't access the timeout setting. Did I miss anything? |
@zliang-akamai Thanks for testing this out! I'm not sure if Terraform respects the test context deadline or the configurable timeout (or both), but I'll do some testing and push up a commit to address this. From a user perspective, I think it makes sense for us to bump the default timeout or at least inform the user to configure a longer timeout period. |
docs/resources/instance.md
Outdated
@@ -271,7 +273,7 @@ The following arguments are available in an `ipv4` configuration block of an `in | |||
The `timeouts` block allows you to specify [timeouts](https://www.terraform.io/docs/configuration/resources.html#timeouts) for certain actions: |
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.
Timeout doc of Terraform has been moved to here: https://developer.hashicorp.com/terraform/language/resources/syntax#operation-timeouts
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.
Nice catch! I'll address that real quick
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.
Tested locally and looks good to me!
8241fe4
into
linode:proj/unified-migrations
* new: Add support for Unified Migrations (#1150) * WIP * Add region migrations * minor changes * long running test * Update test logic * Support filtering in GetRegionsWithCaps * Add migration_type to ImportStateVerifyIgnore * point at feature branch * Update timeout and docs * Update timeouts link * Bump linodego to v1.27.0 * go mod tidy --------- Co-authored-by: Lena Garber <114949949+lgarber-akamai@users.noreply.github.com>
馃摑 Description
This change adds support for the following new linode_instance
migration_type
field introduced in Unified Migrations project. Additionally this change adds support for cross-region migrations on updates to theregion
field rather than just instance recreation.鉁旓笍 How to Test
E2E Testing:
Cross-Region Migration
NOTE: This test currently needs to be run against prod due to availability limitations.
Resize Migration
Manual Testing
TODO