IMPROVEMENTS:
- Data Source:
azurerm_databricks_workspace
- support for thetags
property [GH-9933] azurerm_api_management
- supportConsumption_0
for thesku_name
property [GH-6868]azurerm_dedicated_host
- support for addtionalsku_name
values [GH-9951]azurerm_log_analytics_linked_service
- add validation for resource ID type [GH-9932]azurerm_log_analytics_linked_service
- update validation to use generated validate functions [GH-9950]azurerm_monitor_diagnostic_setting
- validation thateventhub_authorization_rule_id
is a EventHub Namespace Authorization Rule ID [GH-9914]azurerm_monitor_diagnostic_setting
- validation thatlog_analytics_workspace_id
is a Log Analytics Workspace ID [GH-9914]azurerm_monitor_diagnostic_setting
- validation thatstorage_account_id
is a Storage Account ID [GH-9914]azurerm_network_security_rule
- increase allowed the number ofapplication_security_group
blocks allowed [GH-9884]
BUG FIXES:
azurerm_cosmosdb_account
- always includekey_vault_id
in update requests for azure policy enginer compatibility [GH-9966]
UPGRADE NOTES:
azurerm_key_vault
- Azure will be introducing a breaking change on December 31st, 2020 by force-enabling Soft Delete on all new and existing Key Vaults. To workaround this, this release of the Azure Provider still allows you to configure Soft Delete on before this date (but once this is enabled this cannot be disabled). Since new Key Vaults will automatically be provisioned using Soft Delete in the future, and existing Key Vaults will be upgraded - a future release will deprecate thesoft_delete_enabled
field and default this to true early in 2021. (#9911)azurerm_key_vault_certificate
- Terraform will now attempt topurge
Certificates during deletion due to the upcoming breaking change in the Azure API where Key Vaults will have soft-delete force-enabled. This can be disabled by setting thepurge_soft_delete_on_destroy
field within thefeatures -> keyvault
block tofalse
. (#9911)azurerm_key_vault_key
- Terraform will now attempt topurge
Keys during deletion due to the upcoming breaking change in the Azure API where Key Vaults will have soft-delete force-enabled. This can be disabled by setting thepurge_soft_delete_on_destroy
field within thefeatures -> keyvault
block tofalse
. (#9911)azurerm_key_vault_secret
- Terraform will now attempt topurge
Secrets during deletion due to the upcoming breaking change in the Azure API where Key Vaults will have soft-delete force-enabled. This can be disabled by setting thepurge_soft_delete_on_destroy
field within thefeatures -> keyvault
block tofalse
. (#9911)
FEATURES:
- New Resource:
azurerm_eventgrid_system_topic_event_subscription
(#9852) - New Resource:
azurerm_media_job
(#9859) - New Resource:
azurerm_media_streaming_endpoint
(#9537) - New Resource:
azurerm_subnet_service_endpoint_storage_policy
(#8966) - New Resource:
azurerm_synapse_managed_private_endpoint
(#9260)
IMPROVEMENTS:
azurerm_app_service
- Add support foroutbound_ip_address_list
andpossible_outbound_ip_address_list
(#9871)azurerm_disk_encryption_set
- support for updatingkey_vault_key_id
(#7913)azurerm_iot_time_series_insights_gen2_environment
- exposingdata_access_fqdn
(#9848)azurerm_key_vault_certificate
- performing a "purge" of the Certificate during deletion if the feature is opted-in within thefeatures
block, see the "Upgrade Notes" for more information (#9911)azurerm_key_vault_key
- performing a "purge" of the Key during deletion if the feature is opted-in within thefeatures
block, see the "Upgrade Notes" for more information (#9911)azurerm_key_vault_secret
- performing a "purge" of the Secret during deletion if the feature is opted-in within thefeatures
block, see the "Upgrade Notes" for more information (#9911)azurerm_log_analytics_linked_service
- Add new fieldsworkspace_id
,read_access_id
, andwrite_access_id
(#9410)azurerm_linux_virtual_machine
- Normalise SSH keys to cover VM import cases (#9897)azurerm_subnet
- support for theservice_endpoint_policy
block (#8966)azurerm_traffic_manager_profile
- support for new fieldmax_return
and support fortraffic_routing_method
to beMultiValue
(#9487)
BUG FIXES:
azurerm_key_vault_certificate
- readingdns_names
andemails
within thesubject_alternative_names
block from the Certificate if not returned from the API (#8631)azurerm_key_vault_certificate
- polling until the Certificate is fully deleted during deletion (#9911)azurerm_key_vault_key
- polling until the Key is fully deleted during deletion (#9911)azurerm_key_vault_secret
- polling until the Secret is fully deleted during deletion (#9911)azurerm_log_analytics_workspace
- adding a state migration to correctly update the Resource ID (#9853)
For information on changes between the v2.40.0 and v2.0.0 releases, please see the previous v2.x changelog entries.
For information on changes in version v1.44.0 and prior releases, please see the v1.x changelog.