What’s new with Microsoft in open-source and Kubernetes at KubeCon North America 2024
At Microsoft, we are committed to innovation in the cloud-native ecosystem through…
In order to provide more clarity into what’s changed in each Terraform AzureRM provider release, we’re kicking off a blog series that will provide the highlights for each release. We will continue to provide details on every release in the Change Log for the provider within the GitHub repo as well.
If you are looking for what’s coming up in future releases, we are marking issues that we expect to include in the next release or two by adding the appropriate milestones, which correlate with the release versions. For these details, you can check out the milestones section of the AzureRM repo.
The v1.22 release includes a few new resources, which are duplicates of existing resources. The purpose of this is to correct some invalid naming so that we can remove the mis-named resources in the next major version of the Provider (version 2.0.0). Unless otherwise noted each new resource provides the same functionality as the depreciated resource.
As of this release, we are depreciating a few resource properties. Your current configurations will not break with these changes. However, you should begin to migrate away from the depreciated properties so that your configuration aren’t broken by a future release.
Resource/data source | Added property | Depreciated property |
azurerm_application_gateway | fqdns | fqdn_list |
azurerm_application_gateway | ip_addresses | ip_address_list |
azurerm_network_interface |
use azurerm_network_interface_application_ security_group_association instead |
application_security_group_ids |
azurerm_key_vault_key | key_vault_id | vault_uri |
azurerm_key_vault_secret | key_vault_id | vault_uri |
azurerm_key_vault_certificate | key_vault_id | vault_uri |
azurerm_key_vault_access_policy |
vault_name resource_group_name |
key_vault_id |
This release includes numerous other improvements and bug fixes. For the full list please reference the Change Log. Here are a few of the highlights:
Let us know in the comments if you have any questions or suggestions to make these updates more useful for you.