Updated Release Notes

zscaler · Aug 30, 2022 · 589d9c4 · 589d9c4
1 parent eb49f9c
commit 589d9c4
Show file tree

Hide file tree

Showing 4 changed files with 21 additions and 2 deletions.
diff --git a/docs/guides/release-notes.md b/docs/guides/release-notes.md
@@ -12,10 +12,26 @@ Track all ZPA Terraform provider's releases. New resources, features, and bug fi
 
 ---
 
-``Last updated: v2.3.0``
+``Last updated: v2.3.1``
 
 ---
 
+## 2.3.1
+
+### Notes
+
+- Release date: **(August 17 2022)**
+- Supported Terraform version: **v1.x**
+
+### Bug Fixes
+
+- [PR #169](https://github.com/zscaler/terraform-provider-zpa/pull/169) Fixed policy rule order, where the rule order in the UI didn't correspond to the desired order set in HCL. Issue [[#166](https://github.com/zscaler/terraform-provider-zpa/issues/166)]
+- [PR #170](https://github.com/zscaler/terraform-provider-zpa/pull/170) Fixed special character encoding, where certain symbols caused Terraform to indicate potential configuration drifts. Issue [[#149](https://github.com/zscaler/terraform-provider-zpa/issues/149)]
+- [PR #171](https://github.com/zscaler/terraform-provider-zpa/pull/171) Fixed policy configuration attributes where i.e SCIM_GROUPs were causing drifts without changes have been performed. Issue [[#165](https://github.com/zscaler/terraform-provider-zpa/issues/165)]
+- [PR #175](https://github.com/zscaler/terraform-provider-zpa/pull/175) Fixed application segment drifts caused by tcp & udp ports.
+- [PR #176](https://github.com/zscaler/terraform-provider-zpa/pull/176) Fixed application segment PRA drifts caused by tcp & udp ports.
+- [PR #177](https://github.com/zscaler/terraform-provider-zpa/pull/177) Fixed application segment Inspection drifts caused by tcp & udp ports.
+
 ## 2.3.0
 
 ### Notes

diff --git a/docs/resources/zpa_application_segment.md b/docs/resources/zpa_application_segment.md
@@ -147,6 +147,7 @@ The following arguments are supported:
 * `udp_port_ranges` - (Required) UDP port ranges used to access the app.
 
 -> **NOTE:**  TCP and UDP ports can also be defined using the following model:
+-> **NOTE:** When removing TCP and/or UDP ports, parameter must be defined but set as empty due to current API behavior.
 
 * `tcp_port_range` - (Required) TCP port ranges used to access the app.
   * `from:`
@@ -156,6 +157,7 @@ The following arguments are supported:
   * `from:`
   * `to:`
 
+
 ## Attributes Reference
 
 * `description` - (Optional) Description of the application.
@@ -167,7 +169,6 @@ The following arguments are supported:
 * `health_check_type` (Optional)
 * `icmp_access_type` - (Optional)
 * `ip_anchored` - (Optional)
-* `select_connector_close_to_app` - (Optional) This parameter is only supporte for TCP applications.
 * `is_cname_enabled` - (Optional) Indicates if the Zscaler Client Connector (formerly Zscaler App or Z App) receives CNAME DNS records from the connectors.
 * `log_features` - (Optional)
 * `passive_health_enabled` - (Optional)

diff --git a/docs/resources/zpa_application_segment_inspection.md b/docs/resources/zpa_application_segment_inspection.md
@@ -65,6 +65,7 @@ The following arguments are supported:
 * `udp_port_ranges` - (Required) UDP port ranges used to access the app.
 
 -> **NOTE:**  TCP and UDP ports can also be defined using the following model:
+-> **NOTE:** When removing TCP and/or UDP ports, parameter must be defined but set as empty due to current API behavior.
 
 * `tcp_port_range` - (Required) TCP port ranges used to access the app.
   * `from:`

diff --git a/docs/resources/zpa_application_segment_pra.md b/docs/resources/zpa_application_segment_pra.md
@@ -69,6 +69,7 @@ The following arguments are supported:
 * `udp_port_ranges` - (Required) UDP port ranges used to access the app.
 
 -> **NOTE:**  TCP and UDP ports can also be defined using the following model:
+-> **NOTE:** When removing TCP and/or UDP ports, parameter must be defined but set as empty due to current API behavior.
 
 * `tcp_port_range` - (Required) TCP port ranges used to access the app.
   * `from:`