You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Terraform adoption grows, users may begin with a single root module and end up with a lot of code which then needs refactoring in the sense of breaking it down to different modules.
This is usually mostly done by manually copying and pasting blocks around and adding moved {} blocks where existing state is involved. Such process can be laborious and the server could make it easier.
The moved block could be optional and maybe have sensible default either to generate it, or base it on whether there is a backend block and/or existing state.
The text was updated successfully, but these errors were encountered:
Background
As Terraform adoption grows, users may begin with a single root module and end up with a lot of code which then needs refactoring in the sense of breaking it down to different modules.
This is usually mostly done by manually copying and pasting blocks around and adding
moved {}
blocks where existing state is involved. Such process can be laborious and the server could make it easier.For example, the user may start with
./main.tf
and expects to end up with a new module/folder in
./network
and
./network/main.tf
and a modified
./main.tf
Proposal
resource
to an existing moduledata
to an existing moduleresource
to a new moduledata
to a new moduleThe
moved
block could be optional and maybe have sensible default either to generate it, or base it on whether there is abackend
block and/or existing state.The text was updated successfully, but these errors were encountered: