v2.3.0
Breaking Changes
On March 31st 2025 Azure will block the creation of basic public IP addresses, prior to this version would still create basic sku public IP's which is when the field private_virtual_network_with_public_ip is set, which enables bringing your own virtual network and subnet, and having the plugin create a network interface and public IP to connect to the build virtual machine from the host machine.
As of v2.3.0 a standard SKU Public IP Address will be created in Azure, however standard SKU Public IP's require a network security group to define any ingress, otherwise it is all blocked. This means users will need to create a network security group to allow ingress to their virtual networks.
There is an open request to allow Packer to create a network security group for users this was opened before this change. This can cause conflicts with the subnet's network security group, but since we expect that users may run into change, we will likely need to add support for Packer creating the NSG at a NIC level. If you have any feedback on how we address this problem, please reach out here #468 asap.
If you are using private_virtual_network_with_public_ip, you should upgrade to this release by March 31st 2025 or your builds will likely start failing.
You can read more about this deprecation in this official post from Microsoft
If you want to roll back to the previous behavior for this you can set the public_ip_sku field to Basic, but this will stop working on March 31st as stated above
What's Changed
Other Changes
- Bump github.com/hashicorp/packer-plugin-sdk from 0.5.4 to 0.6.0 by @dependabot in #464
- Make it clearer where users can find a target_region example by @JenGoldstrich in #470
- Use Standard IP SKU by default for edge case with
private_virtual_network_with_public_ipfield by @JenGoldstrich in #469
Full Changelog: v2.2.1...v2.3.0