search

Azure / terraform-azurerm-avm-res-network-virtualnetwork

Azure Verified Module for Virtual Network
https://registry.terraform.io/modules/Azure/avm-res-network-virtualnetwork
MIT License
17 stars 14 forks source link

[AVM Question/Feedback]: Migrating from v0.1.x to v0.2.x #98

Open captainhook opened 1 week ago

captainhook commented 1 week ago

Check for previous/existing GitHub issues

Description

Is there any advice/guidance around migrating to version 0.2.x of this module due to the breaking changes? i.e. what can be done to avoid having to destroy and redeploy the virtual network, subnets, and peering?

This might be a good piece of documentation for early adopters of this module.

Thanks, appreciate the support.

microsoft-github-policy-service[bot] commented 1 week ago

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!NOTE] This label was added as per ITA06.

microsoft-github-policy-service[bot] commented 3 days ago

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!

[!NOTE] This message was posted as per ITA01TF.

matt-FFFFFF commented 3 days ago

Hi!

With this sort of change I'd recommend leaving your existing resources on the old version and deploying new ones with the new version.

If you want to migrate you can use import/removed {} blocks to achieve this.

We will provide documentation on how to do this.