Skip to content

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

v0.4.0

26 Jul 13:14
0b98468
Compare
Choose a tag to compare

What's Changed

Added the capability to properly peer by subnet and fixed a non-backwards compatible default on peering.

Full Changelog: v0.3.0...v0.4.0

v0.3.0

17 Jul 15:51
5b60a9a
Compare
Choose a tag to compare

What's Changed

We added some missing properties and enabled automatic feature enablement for some preview features.

We added the address_prefix singular vartiable to the subnet submodule to support some cases where the address_prefixes variable is not being read by resources that use a subnet.

Full Changelog: v0.2.4...v0.3.0

v0.2.4

05 Jul 16:03
5345774
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.2.3...v0.2.4

v0.2.3

30 May 10:17
ff05688
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.2.2...v0.2.3

v0.2.2

29 May 08:43
399aa84
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.2.1...v0.2.2

v0.2.1

28 May 17:13
ae375f1
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.2.0...v0.2.1

v0.2.0

28 May 09:40
8949f54
Compare
Choose a tag to compare

Breaking Changes

v0.2.0 is a re-write of the module, it changes the interface and internal implementation considerably and you will have to update any code and state that is dependent on this module. We try to avoid making updates like this, but in this case we considered the updates valuable enough to make this change. The interface will be stable moving forward.

What's Changed

v0.2.0 moves the module to an AzAPI implementation. The primary driver for this is to support customers that implement common landing zone policies requiring route table and network security groups. You are now able to create a virtual network that meets your policy requirements in one atomic operation avoiding issues with policy blocking deployment.

We have also updated the module to better support common subscription vending scenarios, where application teams manage subnets, but don't managed the virtual network or peering.

We have broken out subnet and peering in sub modules that can be consumed independently. See the documentation and examples for more details on this.

A huge thanks to @kewalaka and @haflidif for all the work on this.

New Contributors

Full Changelog: v0.1.4...v0.2.0

v0.1.4

20 Mar 08:26
968c22c
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.1.3...v0.1.4

v0.1.3

05 Dec 02:11
5325602
Compare
Choose a tag to compare

What's Changed

  • Update avmrequiredfiles.yml by @herms14 in #21
  • Update avmrequiredfiles.yml by @herms14 in #24
  • Fixed subnet creation and other fixes by @herms14 in #20
  • Minimum terraform version should be 1.5.0 to use strcontains function by @chianw in #23

New Contributors

Full Changelog: v0.1.1...v0.1.3

v0.1.2

04 Dec 08:57
686ad69
Compare
Choose a tag to compare
  • changed approach in defining subnets
  • removed ability to create a DDOS plan as this should be a separate module. This module still accepts an existing ddos plan to be integrated to the vnet
  • added capability create a one side peer to another existing vnet