Skip to content
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

[Question/Feedback]: Refactoring to AVM #1800

Open
1 task done
PbALpi7xEX opened this issue Jan 20, 2025 · 1 comment
Open
1 task done

[Question/Feedback]: Refactoring to AVM #1800

PbALpi7xEX opened this issue Jan 20, 2025 · 1 comment
Labels
Needs: Triage 🔍 Maintainers need to triage still Type: Question/Feedback 🙋 Further information is requested or just some feedback

Comments

@PbALpi7xEX
Copy link

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Description

Is Terraform refactoring using "moved" blocks supported and/or recommended when moving existing infrastructure built with custom or community provided modules?

eg:

 moved {
   from = module.vnet["primary"].azurerm_virtual_network.vnet
   to = module.avm-res-network-virtualnetwork.azapi_resource.vnet
 }
moved {
   from = module.vnet["primary"].azurerm_subnet.subnet_for_each["subnet1"]
   to = module.avm-res-network-virtualnetwork.module.subnet["subnet1"].azapi_resource.subnet
 }
@PbALpi7xEX PbALpi7xEX added Needs: Triage 🔍 Maintainers need to triage still Type: Question/Feedback 🙋 Further information is requested or just some feedback labels Jan 20, 2025

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the AVM Issue Triage documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage 🔍 Maintainers need to triage still Type: Question/Feedback 🙋 Further information is requested or just some feedback
Projects
None yet
Development

No branches or pull requests

1 participant