Skip to content

Commit

Permalink
Update changelog for #9117
Browse files Browse the repository at this point in the history
  • Loading branch information
manicminer committed Nov 19, 2020
1 parent 6cb530a commit 4ea209a
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,20 @@ IMPROVEMENTS:
* Data Source: `azurerm_kubernetes_node_pool` - exposing `os_disk_type` [GH-9166]
* `azurerm_api_management_api_diagnostic` - support for the `always_log_errors`, `http_correlation_protocol`, `log_client_ip` and `verbosity` attributes [GH-9172]
* `azurerm_api_management_api_diagnostic` - support the `frontend_request`, `frontend_response`, `backend_request` and `backend_response` blocks [GH-9172]
* `azurerm_dns_zone` - support for the `soa_record` block [GH-9319]
* `azurerm_container_group` - support for secret container volumes with the `container.#.volume.#.secret` attribute [GH-9117]
* `azurerm_cosmosdb_cassandra_keyspace` - `throughput` can now be set to higher than `1000000` if enabled by Azure Support [GH-9050]
* `azurerm_cosmosdb_gremlin_database` - `throughput` can now be set to higher than `1000000` if enabled by Azure Support [GH-9050]
* `azurerm_cosmosdb_mongo_database` - `throughput` can now be set to higher than `1000000` if enabled by Azure Support [GH-9050]
* `azurerm_cosmosdb_sql_container` - `max_throughput` within the `autoscale_settings` block can now be set to higher than `1000000` if enabled by Azure Support [GH-9050]
* `azurerm_cosmosdb_sql_database` - `throughput` can now be set to higher than `1000000` if enabled by Azure Support [GH-9050]
* `azurerm_cosmosdb_table` - `throughput` can now be set to higher than `1000000` if enabled by Azure Support [GH-9050]
* `azurerm_dns_zone` - support for the `soa_record` block [GH-9319]
* `azurerm_firewall` - support for `firewall_policy_id`, `sku_name`, `sku_tier` and `virtual_hub` [GH-8879]
* `azurerm_kubernetes_cluster` - support for configuring `os_disk_type` within the `default_node_pool` block [GH-9166]
* `azurerm_kubernetes_cluster` - `max_count` within the `default_node_pool` block can now be set to a maximum value of `1000` [GH-9227]
* `azurerm_kubernetes_cluster` - `min_count` within the `default_node_pool` block can now be set to a maximum value of `1000` [GH-9227]
* `azurerm_kubernetes_cluster` - `node_count` within the `default_node_pool` block can now be set to a maximum value of `1000` [GH-9227]
* `azurerm_kubernetes_cluster` - the block `http_application_routing` within the `addon_profile` block can now be updated/removed [GH-9358]
* `azurerm_kubernetes_node_pool` - support for configuring `os_disk_type` [GH-9166]
* `azurerm_kubernetes_node_pool` - `max_count` can now be set to a maximum value of `1000` [GH-9227]
* `azurerm_kubernetes_node_pool` - `min_count` can now be set to a maximum value of `1000` [GH-9227]
Expand All @@ -37,7 +39,6 @@ IMPROVEMENTS:
* `azurerm_linux_virtual_machine` - updating the `dedicated_host_id` no longer forces a new resource [GH-9264]
* `azurerm_linux_virtual_machine` - support for graceful shutdowns (via the features block) [GH-8470]
* `azurerm_linux_virtual_machine_scale_set` - support for the `platform_fault_domain_count`, `disk_iops_read_write`, and `disk_mbps_read_write` properties [GH-9262]
* `azurerm_kubernetes_cluster` - the block `http_application_routing` within the `addon_profile` block can now be updated/removed [GH-9358]
* `azurerm_mssql_database` - `sku_name` supports more `DWxxxc` options [GH-9370]
* `azurerm_policy_set_definition` - support for the `policy_definition_group` block [GH-9259]
* `azurerm_postgresql_server` - increase max storage to 16TiB [GH-9373]
Expand Down

0 comments on commit 4ea209a

Please sign in to comment.