jprdonnelly/opentf
1
0
Fork 0
mirror of https://github.com/opentffoundation/opentf.git synced 2025-12-25 01:00:16 -05:00
Code Issues Packages Projects Releases Wiki Activity

Moved for different types (#2370)

Browse Source 
Signed-off-by: Christian Mesh <christianmesh1@gmail.com>
Signed-off-by: Ilia Gogotchuri <ilia.gogotchuri0@gmail.com>
Co-authored-by: Christian Mesh <christianmesh1@gmail.com>
This commit is contained in:
Ilia Gogotchuri
2025-02-05 15:14:19 +04:00
committed by GitHub
parent 9b9ae4a25e
commit 5968e195b0
21 changed files with 1434 additions and 187 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
website/docs/language/modules/develop/refactoring.mdx
View File

@@ -45,6 +45,7 @@ describe several refactoring use-cases and the appropriate addressing syntax
for each situation.
* [Renaming a Resource](#renaming-a-resource)
* [Changing a Resource Type](#changing-a-resource-type)
* [Enabling `count` or `for_each` For a Resource](#enabling-count-or-for_each-for-a-resource)
* [Renaming a Module Call](#renaming-a-module-call)
* [Enabling `count` or `for_each` For a Module Call](#enabling-count-or-for_each-for-a-module-call)
@@ -96,11 +97,15 @@ so OpenTofu recognizes the move for all instances of the resource. That is,
it covers both `aws_instance.a[0]` and `aws_instance.a[1]` without the need
to identify each one separately.
Each resource type has a separate schema and so objects of different types
are not compatible. Therefore, although you can use `moved` to change the name
of a resource, you _cannot_ use `moved` to change to a different resource type
or to change a managed resource (a `resource` block) into a data resource
(a `data` block).
## Changing a Resource Type
Each resource type has a separate schema, so objects of different types are not generally compatible.
However, some providers will let you change an object from one resource type to another.
It is also possible to change one provider's resource to another provider's resource, as long as the new provider supports migration from the old resource.
Refer to the provider documentation for more information about resource compatibility.
You can use `moved` to change the name (and sometimes type) of a resource,
but you _cannot_ use `moved` to change a managed resource (a `resource` block) into a data resource (a `data` block).
## Enabling `count` or `for_each` For a Resource