Integration in CI/CD pipeline when there are also non-migration changes about tfmigrate HOT 3 CLOSED

Hi @WVan, Thank you for sharing your use-case!

It looks like a problem similar to #36. It had been implemented in #37, but it was recently deprecated in #63 due to a change in Terraform 1.1. At time of this writing with the latest tfmigrate v0.3.0 + Terraform v1.1.0, there is no perfect single solution due to some technical constraints.

Knowing that not all use cases can be covered, but the following might be help:

• For renaming a resource address in a single tfstate, use a new moved block introduced in Terraform 1.1. See https://www.hashicorp.com/blog/terraform-1-1-improves-refactoring-and-the-cloud-cli-experience
• For moving a resource accross two tfstates, use a multi_state migration in tfmigrate and not to include other normal configuration changes in a single pull request.
• For importing or removing a resource in a single tfstate, use a state migration in tfmigrate with setting a force attribute to true, which allows you to apply migration even if it contains some plan changes, finally run a normal terraform apply to converge changes.

A native plannable import feature has been proposed in the upstream, but not implemented yet. hashicorp/terraform#26364

from tfmigrate.

After thinking about how to implement a pipeline, you may simplify them into the 3rd case because your pipeline already has a step for an approval before terraform apply, which allows you to review changes ignored by tfmigrate apply with the force attribute.

from tfmigrate.

I'm going to close this because there has been no activity on this recently. Please feel free to reopen this if you have any questions or suggestions. Thanks!

from tfmigrate.