You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/5.0-upgrade-guide.html.markdown
+52-6Lines changed: 52 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,6 +74,7 @@ provider "azurerm" {
74
74
features {}
75
75
}
76
76
```
77
+
77
78
##### How to replicate the previous behaviour
78
79
79
80
If you want to maintain the v4.x behaviour and automatically register the same set of Resource Providers as before, explicitly set `resource_provider_registrations` to the `legacy` resource provider set in your provider block:
@@ -87,7 +88,6 @@ provider "azurerm" {
87
88
88
89
For more information, see the [Resource Provider Registrations](index.html#resource-provider-registrations) section in the provider documentation.
89
90
90
-
91
91
#### Enhanced Validation Default Changed
92
92
93
93
The enhanced validation feature, which caches supported Azure regions and Resource Providers from the Azure MetaData Service to validate `location` and Resource Provider arguments, now defaults to disabled in version 5.0.
@@ -111,6 +111,53 @@ This change was made because:
111
111
112
112
The legacy `ARM_PROVIDER_ENHANCED_VALIDATION` environment variable, which previously controlled both location and resource provider validation, has been removed in version 5.0. Please migrate to either the `enhanced_validation` provider block or the specific environment variables: `ARM_PROVIDER_ENHANCED_VALIDATION_LOCATIONS` and `ARM_PROVIDER_ENHANCED_VALIDATION_RESOURCE_PROVIDERS`.
113
113
114
+
## AI Services migration to Cognitive Account
115
+
116
+
The `azurerm_ai_services` resource has been removed and replaced by `azurerm_cognitive_account`. The tables below map every attribute from `azurerm_ai_services` to its equivalent in `azurerm_cognitive_account`.
|`customer_managed_key`|`customer_managed_key`| See `customer_managed_key` block below. |
133
+
|`identity`|`identity`| Unchanged. |
134
+
|`network_acls`|`network_acls`| Unchanged. |
135
+
|`storage`|`storage`| Note: the `storage` block was accepted by `azurerm_ai_services` but was not processed; values are now correctly applied by `azurerm_cognitive_account`. |
136
+
|`tags`|`tags`| Unchanged. |
137
+
138
+
~> **Note:** If your configuration included a `storage` block under `azurerm_ai_services`, `terraform plan` may show changes after migration even though the Azure resource itself has not changed. This occurs because `azurerm_ai_services` silently ignored the `storage` block and never sent those values to the API, so the imported state does not reflect them. Running `terraform apply` will reconcile the state by applying the storage configuration for the first time.
~> **Note:** In `azurerm_cognitive_account`, `key_vault_key_id` inside the `customer_managed_key` block is Required, whereas in `azurerm_ai_services` it was Optional (one of `key_vault_key_id` or `managed_hsm_key_id` was required).
Please follow the format in the example below for adding removed resources:
@@ -225,7 +272,6 @@ This deprecated resource has been superseded/retired and has been removed from t
225
272
226
273
* This deprecated resource has been retired and has been removed from the Azure Provider.
227
274
228
-
229
275
## Removed Data Sources
230
276
231
277
Please follow the format in the example below for adding removed data sources:
@@ -262,10 +308,10 @@ Please follow the format in the example below for listing breaking changes in re
262
308
263
309
### `azurerm_api_management`
264
310
265
-
* The deprecated `hostname_configuration.developer_portal.key_vault_id` property has been removed in favour of the ``hostname_configuration.developer_portal.key_vault_certificate_id`` property.
266
-
* The deprecated `hostname_configuration.management.key_vault_id` property has been removed in favour of the ``hostname_configuration.management.key_vault_certificate_id`` property.
267
-
* The deprecated `hostname_configuration.portal.key_vault_id` property has been removed in favour of the ``hostname_configuration.portal.key_vault_certificate_id`` property.
268
-
* The deprecated `hostname_configuration.proxy.key_vault_id` property has been removed in favour of the ``hostname_configuration.proxy.key_vault_certificate_id`` property.
311
+
* The deprecated `hostname_configuration.developer_portal.key_vault_id` property has been removed in favour of the ``hostname_configuration.developer_portal.key_vault_certificate_id`` property.
312
+
* The deprecated `hostname_configuration.management.key_vault_id` property has been removed in favour of the ``hostname_configuration.management.key_vault_certificate_id`` property.
313
+
* The deprecated `hostname_configuration.portal.key_vault_id` property has been removed in favour of the ``hostname_configuration.portal.key_vault_certificate_id`` property.
314
+
* The deprecated `hostname_configuration.proxy.key_vault_id` property has been removed in favour of the ``hostname_configuration.proxy.key_vault_certificate_id`` property.
269
315
* The deprecated `hostname_configuration.scm.key_vault_id` property has been removed in favour of the ``hostname_configuration.scm.key_vault_certificate_id`` property.
270
316
* The deprecated `protocols.enable_http2` property has been removed in favour of the `protocols.http2_enabled` property.
271
317
* The deprecated `security.enable_backend_ssl30` property has been removed in favour of the `security.backend_ssl30_enabled` property.
0 commit comments