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: CHANGELOG.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,12 @@
1
1
## 2.34.0 (Unreleased)
2
2
3
+
UPGRADE NOTES
4
+
5
+
* This release changes the default value for `azurerm_api_management_api.subscription_required` property to `true`. This was the behaviour prior to `v2.15.0` and is a more secure default which will prevent accidently exposing API's.
6
+
3
7
BUG FIXES:
4
8
9
+
*`azurerm_api_management_api` - ensure `subscription_required` defaults to the more secure `true` value as well revery to `v2.15` and lower's behaviour [GH-7963]
5
10
*`log_analytics_workspace` - support for the `daily_quota_gb` property [GH-8861]
6
11
*`azurerm_kubernetes_cluster` - Fix issue where `min_count` and `max_count` couldn't be the equal [GH-8957]
7
12
*`azurerm_signalr_service` - switching the`features` block to a set so order is irrelevant [GH-8815]
@@ -10,7 +15,7 @@ BUG FIXES:
10
15
11
16
UPGRADE NOTES
12
17
13
-
> * This release includes a workaround for [a breaking change in Azure’s API related to the Extended Auditing Policy](https://github.com/Azure/azure-rest-api-specs/issues/11271) of the SQL and MSSQL resources. The Service Team have confirmed that this Regression will first roll out to all regions before the bug fix is deployed - as such this workaround will be removed in a future release once the fix for the Azure API has been rolled out to all regions.
18
+
* This release includes a workaround for [a breaking change in Azure’s API related to the Extended Auditing Policy](https://github.com/Azure/azure-rest-api-specs/issues/11271) of the SQL and MSSQL resources. The Service Team have confirmed that this Regression will first roll out to all regions before the bug fix is deployed - as such this workaround will be removed in a future release once the fix for the Azure API has been rolled out to all regions.
0 commit comments