Azure/terraform-azurerm-avm-ptn-alz-connectivity-virtual-wan v0.13.0

on GitHub

Breaking changes

This release includes a refactor of the underlying private link private DNS zone pattern module. This was done to support resolution policy, better performance, standardization, and maintainability. As such, the interface for the private DNS zones section of this module has been updated to match.

Where possible we have implemented moved blocks to migrate state. Due to the limitations of moved block capabilities we have been unable to cover all scenarios for virtual network links, but we have added a set of blocks for the standard ALZ settings.

If these blocks don't cover your scenario, you may see that your Terraform plan indicates it will destroy and recreate some virtual network links. If that is the case, you'll need to add some moved blocks.

We have added a temporary output called private_link_private_dns_zone_virtual_network_link_moved_blocks that will output the necessary moved blocks for your configuration. If you are using this module via the accelerator, then refer to the v13 release notes for the instructions to add the blocks.

If you are using this module in your own code, follow these steps to generate the moved blocks and add them to your configuration:

1. Follow your normal process, to clone the repo and create a branch
2. Make any changes to inputs you need to for DNS zones.
3. Map the private_link_private_dns_zone_virtual_network_link_moved_blocks output from this module to an output in your parent module
4. Commit and push your changes to your branch
5. Create a pull request to your main branch, but do not merge it yet
6. Wait for the CI pipeline to run and navigate to the plan stage and step
7. Look for the output you created and copy all the moved blocks from that variable.
8. Create a new file called moved.tf (or whatever name you prefer) in the root of your repo and paste the moved blocks into that file.
9. Run terraform fmt to format the file correctly.
10. Commit and push the new file to your branch.
11. Now wait for the CI pipeline to run again. This time when you examine the plan you should not see any unexpected resource destruction and recreation.
12. Once you are satisfied with the plan, you can merge your pull request and trigger the CD pipeline as normal.

What's Changed

• chore: pre-commit updates by @azure-verified-modules[bot] in #69
• feat: dns resolution policy by @jaredfholgate in #70

Full Changelog: v0.12.2...v0.13.0