@robinmordasiewicz/f5xc-terraform-mcp 3.10.2 → 3.10.4

package/dist/docs/resources/cloud_connect.md

@@ -128,7 +128,7 @@ A [`vpc_list`](#aws-tgw-site-vpc-attachments-vpc-list) block (within [`aws_tgw_s
 
 <a id="labels-3555f3"></a>&#x2022; [`labels`](#labels-3555f3) - Optional Block<br>Add labels for the VPC attachment. These labels can then be used in policies such as enhanced firewall
 
-<a id="routing-97ae2a"></a>&#x2022; [`manual_routing`](#routing-97ae2a) - Optional Block<br>Can be used for messages where no values are needed
+<a id="routing-97ae2a"></a>&#x2022; [`manual_routing`](#routing-97ae2a) - Optional Block<br>Enable this option
 
 <a id="vpc-id-318c59"></a>&#x2022; [`vpc_id`](#vpc-id-318c59) - Optional String<br>Enter the VPC ID of the VPC to be attached
 
@@ -182,7 +182,7 @@ A [`vnet_list`](#list-5826e3) block (within [`azure_vnet_site.vnet_attachments`]
 
 <a id="labels-e777f2"></a>&#x2022; [`labels`](#labels-e777f2) - Optional Block<br>Add labels for the VNET attachments. These labels can then be used in policies such as enhanced firewall policies
 
-<a id="routing-e423fa"></a>&#x2022; [`manual_routing`](#routing-e423fa) - Optional Block<br>Can be used for messages where no values are needed
+<a id="routing-e423fa"></a>&#x2022; [`manual_routing`](#routing-e423fa) - Optional Block<br>Enable this option
 
 <a id="subscription-id-9a0b4f"></a>&#x2022; [`subscription_id`](#subscription-id-9a0b4f) - Optional String<br>Enter the Subscription ID of the VNET to be attached
 

package/dist/docs/resources/cloud_credentials.md

@@ -88,9 +88,9 @@ An [`aws_assume_role`](#aws-assume-role) block supports the following:
 
 <a id="aws-assume-role-duration-seconds"></a>&#x2022; [`duration_seconds`](#aws-assume-role-duration-seconds) - Optional Number<br>The duration, in seconds of the role session
 
-<a id="aws-assume-role-external-id-is-optional"></a>&#x2022; [`external_id_is_optional`](#aws-assume-role-external-id-is-optional) - Optional Block<br>Can be used for messages where no values are needed
+<a id="aws-assume-role-external-id-is-optional"></a>&#x2022; [`external_id_is_optional`](#aws-assume-role-external-id-is-optional) - Optional Block<br>Enable this option
 
-<a id="tenant-id-b8874c"></a>&#x2022; [`external_id_is_tenant_id`](#tenant-id-b8874c) - Optional Block<br>Can be used for messages where no values are needed
+<a id="tenant-id-b8874c"></a>&#x2022; [`external_id_is_tenant_id`](#tenant-id-b8874c) - Optional Block<br>Enable this option
 
 <a id="aws-assume-role-role-arn"></a>&#x2022; [`role_arn`](#aws-assume-role-role-arn) - Optional String<br>IAM Role ARN to assume the role
 

package/dist/docs/resources/cloud_link.md

@@ -71,7 +71,7 @@ resource "f5xc_cloud_link" "example" {
 <br><br>&#x2022; <a id="gcp"></a>[`gcp`](#gcp) - Optional Block<br>Google Cloud Platform (GCP) CloudLink Provider. CloudLink for GCP Cloud Provider<br>See [GCP](#gcp) below for details.
 
 -> **One of the following:**
-&#x2022; <a id="disabled"></a>[`disabled`](#disabled) - Optional Block<br>Can be used for messages where no values are needed
+&#x2022; <a id="disabled"></a>[`disabled`](#disabled) - Optional Block<br>Enable this option
 <br><br>&#x2022; <a id="enabled"></a>[`enabled`](#enabled) - Optional Block<br>CloudLink ADN Network Config<br>See [Enabled](#enabled) below for details.
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
@@ -126,7 +126,7 @@ A [`connections`](#aws-byoc-connections) block (within [`aws.byoc`](#aws-byoc))
 
 <a id="aws-byoc-connections-region"></a>&#x2022; [`region`](#aws-byoc-connections-region) - Optional String<br>Region where the connection is setup
 
-<a id="name-ebc6a3"></a>&#x2022; [`system_generated_name`](#name-ebc6a3) - Optional Block<br>Can be used for messages where no values are needed
+<a id="name-ebc6a3"></a>&#x2022; [`system_generated_name`](#name-ebc6a3) - Optional Block<br>Enable this option
 
 <a id="aws-byoc-connections-tags"></a>&#x2022; [`tags`](#aws-byoc-connections-tags) - Optional Block<br>AWS Tags is a label consisting of a user-defined key and value. It helps to manage, identify, organize, search for, and filter resources in AWS console. Specified tags will be added to Virtual interface along with any F5XC specific tags
 
@@ -200,7 +200,7 @@ A [`connections`](#gcp-byoc-connections) block (within [`gcp.byoc`](#gcp-byoc))
 
 <a id="gcp-byoc-connections-region"></a>&#x2022; [`region`](#gcp-byoc-connections-region) - Optional String<br>GCP Region in which the GCP Cloud Interconnect attachment is configured
 
-<a id="gcp-byoc-connections-same-as-credential"></a>&#x2022; [`same_as_credential`](#gcp-byoc-connections-same-as-credential) - Optional Block<br>Can be used for messages where no values are needed
+<a id="gcp-byoc-connections-same-as-credential"></a>&#x2022; [`same_as_credential`](#gcp-byoc-connections-same-as-credential) - Optional Block<br>Enable this option
 
 #### GCP Byoc Connections Metadata
 

package/dist/docs/resources/cluster.md

@@ -32,7 +32,7 @@ resource "f5xc_cluster" "example" {
   }
 
   # Resource-specific configuration
-  # [OneOf: auto_http_config, http1_config, http2_options] Ca...
+  # [OneOf: auto_http_config, http1_config, http2_options] En...
   auto_http_config {
     # Configure auto_http_config settings
   }
@@ -67,7 +67,7 @@ resource "f5xc_cluster" "example" {
 ### Spec Argument Reference
 
 -> **One of the following:**
-&#x2022; <a id="auto-http-config"></a>[`auto_http_config`](#auto-http-config) - Optional Block<br>Can be used for messages where no values are needed
+&#x2022; <a id="auto-http-config"></a>[`auto_http_config`](#auto-http-config) - Optional Block<br>Enable this option
 <br><br>&#x2022; <a id="http1-config"></a>[`http1_config`](#http1-config) - Optional Block<br>HTTP/1.1 Protocol OPTIONS for upstream connections<br>See [Http1 Config](#http1-config) below for details.
 <br><br>&#x2022; <a id="http2-options"></a>[`http2_options`](#http2-options) - Optional Block<br>Http2 Protocol OPTIONS for upstream connections<br>See [Http2 Options](#http2-options) below for details.
 
@@ -78,8 +78,8 @@ resource "f5xc_cluster" "example" {
 <a id="default-subset"></a>&#x2022; [`default_subset`](#default-subset) - Optional Block<br>List of key-value pairs that define default subset. This subset can be referred in fallback_policy which gets used when route specifies no metadata or no subset matching the metadata exists
 
 -> **One of the following:**
-&#x2022; <a id="disable-proxy-protocol"></a>[`disable_proxy_protocol`](#disable-proxy-protocol) - Optional Block<br>Can be used for messages where no values are needed
-<br><br>&#x2022; <a id="proxy-protocol-v1"></a>[`proxy_protocol_v1`](#proxy-protocol-v1) - Optional Block<br>Can be used for messages where no values are needed
+&#x2022; <a id="disable-proxy-protocol"></a>[`disable_proxy_protocol`](#disable-proxy-protocol) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="proxy-protocol-v1"></a>[`proxy_protocol_v1`](#proxy-protocol-v1) - Optional Block<br>Enable this option
 
 <a id="endpoint-selection"></a>&#x2022; [`endpoint_selection`](#endpoint-selection) - Optional String  Defaults to `DISTRIBUTED`<br>Possible values are `DISTRIBUTED`, `LOCAL_ONLY`, `LOCAL_PREFERRED`<br>[Enum: DISTRIBUTED|LOCAL_ONLY|LOCAL_PREFERRED] Policy for selection of endpoints from local site/remote site/both Consider both remote and local endpoints for load balancing LOCAL_ONLY: Consider only local endpoints for load balancing Enable this policy to load balance ONLY among locally discovered endpoints Prefer the local endpoints for
 
@@ -96,13 +96,13 @@ resource "f5xc_cluster" "example" {
 <a id="loadbalancer-algorithm"></a>&#x2022; [`loadbalancer_algorithm`](#loadbalancer-algorithm) - Optional String  Defaults to `ROUND_ROBIN`<br>Possible values are `ROUND_ROBIN`, `LEAST_REQUEST`, `RING_HASH`, `RANDOM`, `LB_OVERRIDE`<br>[Enum: ROUND_ROBIN|LEAST_REQUEST|RING_HASH|RANDOM|LB_OVERRIDE] Different load balancing algorithms supported When a connection to a endpoint in an upstream cluster is required, the load balancer uses loadbalancer_algorithm to determine which host is selected. - ROUND_ROBIN: ROUND_ROBIN Policy in which each healthy/available upstream endpoint is selected in
 
 -> **One of the following:**
-&#x2022; <a id="no-panic-threshold"></a>[`no_panic_threshold`](#no-panic-threshold) - Optional Block<br>Can be used for messages where no values are needed
+&#x2022; <a id="no-panic-threshold"></a>[`no_panic_threshold`](#no-panic-threshold) - Optional Block<br>Enable this option
 
 <a id="outlier-detection"></a>&#x2022; [`outlier_detection`](#outlier-detection) - Optional Block<br>Outlier detection and ejection is the process of dynamically determining whether some number of hosts in an upstream cluster are performing unlike the others and removing them from the healthy load balancing set. Outlier detection is a form of passive health checking. Algorithm 1<br>See [Outlier Detection](#outlier-detection) below for details.
 
 <a id="panic-threshold"></a>&#x2022; [`panic_threshold`](#panic-threshold) - Optional Number<br>Configure a threshold (percentage of unhealthy endpoints) below which all endpoints will be considered for loadbalancing ignoring its health status
 
-<a id="proxy-protocol-v2"></a>&#x2022; [`proxy_protocol_v2`](#proxy-protocol-v2) - Optional Block<br>Can be used for messages where no values are needed
+<a id="proxy-protocol-v2"></a>&#x2022; [`proxy_protocol_v2`](#proxy-protocol-v2) - Optional Block<br>Enable this option
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
 
@@ -176,13 +176,13 @@ A [`http1_config`](#http1-config) block supports the following:
 
 A [`header_transformation`](#http1-config-header-transformation) block (within [`http1_config`](#http1-config)) supports the following:
 
-<a id="transformation-489a65"></a>&#x2022; [`default_header_transformation`](#transformation-489a65) - Optional Block<br>Can be used for messages where no values are needed
+<a id="transformation-489a65"></a>&#x2022; [`default_header_transformation`](#transformation-489a65) - Optional Block<br>Enable this option
 
-<a id="transformation-7adc9e"></a>&#x2022; [`legacy_header_transformation`](#transformation-7adc9e) - Optional Block<br>Can be used for messages where no values are needed
+<a id="transformation-7adc9e"></a>&#x2022; [`legacy_header_transformation`](#transformation-7adc9e) - Optional Block<br>Enable this option
 
-<a id="transformation-61c351"></a>&#x2022; [`preserve_case_header_transformation`](#transformation-61c351) - Optional Block<br>Can be used for messages where no values are needed
+<a id="transformation-61c351"></a>&#x2022; [`preserve_case_header_transformation`](#transformation-61c351) - Optional Block<br>Enable this option
 
-<a id="transformation-17cea9"></a>&#x2022; [`proper_case_header_transformation`](#transformation-17cea9) - Optional Block<br>Can be used for messages where no values are needed
+<a id="transformation-17cea9"></a>&#x2022; [`proper_case_header_transformation`](#transformation-17cea9) - Optional Block<br>Enable this option
 
 #### Http2 Options
 
@@ -224,17 +224,17 @@ A [`tls_parameters`](#tls-parameters) block supports the following:
 
 <a id="tls-parameters-common-params"></a>&#x2022; [`common_params`](#tls-parameters-common-params) - Optional Block<br>Information of different aspects for TLS authentication related to ciphers, certificates and trust store<br>See [Common Params](#tls-parameters-common-params) below.
 
-<a id="caching-2e557f"></a>&#x2022; [`default_session_key_caching`](#caching-2e557f) - Optional Block<br>Can be used for messages where no values are needed
+<a id="caching-2e557f"></a>&#x2022; [`default_session_key_caching`](#caching-2e557f) - Optional Block<br>Enable this option
 
-<a id="caching-d819c5"></a>&#x2022; [`disable_session_key_caching`](#caching-d819c5) - Optional Block<br>Can be used for messages where no values are needed
+<a id="caching-d819c5"></a>&#x2022; [`disable_session_key_caching`](#caching-d819c5) - Optional Block<br>Enable this option
 
-<a id="tls-parameters-disable-sni"></a>&#x2022; [`disable_sni`](#tls-parameters-disable-sni) - Optional Block<br>Can be used for messages where no values are needed
+<a id="tls-parameters-disable-sni"></a>&#x2022; [`disable_sni`](#tls-parameters-disable-sni) - Optional Block<br>Enable this option
 
 <a id="tls-parameters-max-session-keys"></a>&#x2022; [`max_session_keys`](#tls-parameters-max-session-keys) - Optional Number<br>Number of session keys that are cached
 
 <a id="tls-parameters-sni"></a>&#x2022; [`sni`](#tls-parameters-sni) - Optional String<br>SNI value to be used
 
-<a id="tls-parameters-use-host-header-as-sni"></a>&#x2022; [`use_host_header_as_sni`](#tls-parameters-use-host-header-as-sni) - Optional Block<br>Can be used for messages where no values are needed
+<a id="tls-parameters-use-host-header-as-sni"></a>&#x2022; [`use_host_header_as_sni`](#tls-parameters-use-host-header-as-sni) - Optional Block<br>Enable this option
 
 #### TLS Parameters Cert Params
 
@@ -308,11 +308,11 @@ A [`tls_certificates`](#certificates-c9caff) block (within [`tls_parameters.comm
 
 <a id="spec-5af02c"></a>&#x2022; [`description_spec`](#spec-5af02c) - Optional String<br>Description. Description for the certificate
 
-<a id="stapling-c091fa"></a>&#x2022; [`disable_ocsp_stapling`](#stapling-c091fa) - Optional Block<br>Can be used for messages where no values are needed
+<a id="stapling-c091fa"></a>&#x2022; [`disable_ocsp_stapling`](#stapling-c091fa) - Optional Block<br>Enable this option
 
 <a id="key-da7979"></a>&#x2022; [`private_key`](#key-da7979) - Optional Block<br>SecretType is used in an object to indicate a sensitive/confidential field<br>See [Private Key](#key-da7979) below.
 
-<a id="defaults-f58bc7"></a>&#x2022; [`use_system_defaults`](#defaults-f58bc7) - Optional Block<br>Can be used for messages where no values are needed
+<a id="defaults-f58bc7"></a>&#x2022; [`use_system_defaults`](#defaults-f58bc7) - Optional Block<br>Enable this option
 
 #### TLS Parameters Common Params TLS Certificates Custom Hash Algorithms
 
@@ -354,9 +354,9 @@ A [`validation_params`](#params-6e95a6) block (within [`tls_parameters.common_pa
 
 An [`upstream_conn_pool_reuse_type`](#upstream-conn-pool-reuse-type) block supports the following:
 
-<a id="reuse-008a14"></a>&#x2022; [`disable_conn_pool_reuse`](#reuse-008a14) - Optional Block<br>Can be used for messages where no values are needed
+<a id="reuse-008a14"></a>&#x2022; [`disable_conn_pool_reuse`](#reuse-008a14) - Optional Block<br>Enable this option
 
-<a id="reuse-ad4462"></a>&#x2022; [`enable_conn_pool_reuse`](#reuse-ad4462) - Optional Block<br>Can be used for messages where no values are needed
+<a id="reuse-ad4462"></a>&#x2022; [`enable_conn_pool_reuse`](#reuse-ad4462) - Optional Block<br>Enable this option
 
 ---
 

package/dist/docs/resources/dc_cluster_group.md

@@ -36,11 +36,11 @@ resource "f5xc_dc_cluster_group" "example" {
   type {
     # Configure type settings
   }
-  # Can be used for messages where no values are needed.
+  # Enable this option
   control_and_data_plane_mesh {
     # Configure control_and_data_plane_mesh settings
   }
-  # Can be used for messages where no values are needed.
+  # Enable this option
   data_plane_mesh {
     # Configure data_plane_mesh settings
   }
@@ -94,9 +94,9 @@ A [`timeouts`](#timeouts) block supports the following:
 
 A [`type`](#type) block supports the following:
 
-<a id="type-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#type-control-and-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
+<a id="type-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#type-control-and-data-plane-mesh) - Optional Block<br>Enable this option
 
-<a id="type-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#type-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
+<a id="type-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#type-data-plane-mesh) - Optional Block<br>Enable this option
 
 ---
 

package/dist/docs/resources/discovery.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_discovery Resource - terraform-provider-f5xc"
 subcategory: "Applications"
 description: |-
-  Manages API discovery creates a new object in the storage backend for metadata.namespace. in F5 Distributed Cloud.
+  Manages a Discovery resource in F5 Distributed Cloud for api to create discovery object for a site or virtual site in system namespace. configuration.
 ---
 
 # f5xc_discovery (Resource)
 
-Manages API discovery creates a new object in the storage backend for metadata.namespace. in F5 Distributed Cloud.
+Manages a Discovery resource in F5 Distributed Cloud for api to create discovery object for a site or virtual site in system namespace. configuration.
 
 ~> **Note** For more information about this resource, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 
@@ -15,7 +15,7 @@ Manages API discovery creates a new object in the storage backend for metadata.n
 
 ```terraform
 # Discovery Resource Example
-# Manages API discovery creates a new object in the storage backend for metadata.namespace. in F5 Distributed Cloud.
+# Manages a Discovery resource in F5 Distributed Cloud for api to create discovery object for a site or virtual site in system namespace. configuration.
 
 # Basic Discovery configuration
 resource "f5xc_discovery" "example" {
@@ -78,10 +78,19 @@ resource "f5xc_discovery" "example" {
 
 ### Spec Argument Reference
 
-<a id="custom-auth-types"></a>&#x2022; [`custom_auth_types`](#custom-auth-types) - Optional Block<br>Select your custom authentication types to be detected in the API discovery<br>See [Custom Auth Types](#custom-auth-types) below for details.
+-> **One of the following:**
+&#x2022; <a id="cluster-id"></a>[`cluster_id`](#cluster-id) - Optional String<br>Specify identifier for discovery cluster. This identifier can be specified in endpoint object to discover only from this discovery object
+
+-> **One of the following:**
+&#x2022; <a id="discovery-consul"></a>[`discovery_consul`](#discovery-consul) - Optional Block<br>Discovery configuration for Hashicorp Consul<br>See [Discovery Consul](#discovery-consul) below for details.
+<br><br>&#x2022; <a id="discovery-k8s"></a>[`discovery_k8s`](#discovery-k8s) - Optional Block<br>K8S Discovery Configuration. Discovery configuration for K8S<br>See [Discovery K8S](#discovery-k8s) below for details.
+
+<a id="no-cluster-id"></a>&#x2022; [`no_cluster_id`](#no-cluster-id) - Optional Block<br>Enable this option
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
 
+<a id="where"></a>&#x2022; [`where`](#where) - Optional Block<br>NetworkSiteRefSelector defines a union of reference to site or reference to virtual_network or reference to virtual_site It is used to determine virtual network using following rules \* Direct reference to virtual_network object \* Site local network when refering to site object \* All site local<br>See [Where](#where) below for details.
+
 ### Attributes Reference
 
 In addition to all arguments above, the following attributes are exported:
@@ -90,13 +99,173 @@ In addition to all arguments above, the following attributes are exported:
 
 ---
 
-#### Custom Auth Types
+#### Discovery Consul
+
+A [`discovery_consul`](#discovery-consul) block supports the following:
+
+<a id="discovery-consul-access-info"></a>&#x2022; [`access_info`](#discovery-consul-access-info) - Optional Block<br>Hashicorp Consul API server information<br>See [Access Info](#discovery-consul-access-info) below.
+
+<a id="discovery-consul-publish-info"></a>&#x2022; [`publish_info`](#discovery-consul-publish-info) - Optional Block<br>VIP Publish Configuration. Consul Configuration to publish VIPs<br>See [Publish Info](#discovery-consul-publish-info) below.
+
+#### Discovery Consul Access Info
+
+An [`access_info`](#discovery-consul-access-info) block (within [`discovery_consul`](#discovery-consul)) supports the following:
+
+<a id="info-c7c3de"></a>&#x2022; [`connection_info`](#info-c7c3de) - Optional Block<br>Configuration details to access discovery service REST API<br>See [Connection Info](#info-c7c3de) below.
+
+<a id="info-28e890"></a>&#x2022; [`http_basic_auth_info`](#info-28e890) - Optional Block<br>Authentication parameters to access Hashicorp Consul<br>See [HTTP Basic Auth Info](#info-28e890) below.
+
+#### Discovery Consul Access Info Connection Info
+
+A [`connection_info`](#info-c7c3de) block (within [`discovery_consul.access_info`](#discovery-consul-access-info)) supports the following:
+
+<a id="server-db3eac"></a>&#x2022; [`api_server`](#server-db3eac) - Optional String<br>API server must be a fully qualified domain string and port specified as host:port pair
+
+<a id="info-72d38f"></a>&#x2022; [`tls_info`](#info-72d38f) - Optional Block<br>TLS config for client of discovery service<br>See [TLS Info](#info-72d38f) below.
+
+#### Discovery Consul Access Info Connection Info TLS Info
+
+<a id="deep-2a9ae1"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery Consul Access Info Connection Info TLS Info Key URL
+
+<a id="deep-9298be"></a>Deeply nested **URL** block collapsed for readability.
+
+#### Discovery Consul Access Info Connection Info TLS Info Key URL Blindfold Secret Info
+
+<a id="deep-14dd70"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery Consul Access Info Connection Info TLS Info Key URL Clear Secret Info
+
+<a id="deep-ed594e"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery Consul Access Info HTTP Basic Auth Info
+
+<a id="deep-bbf940"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery Consul Access Info HTTP Basic Auth Info Passwd URL
+
+<a id="deep-ee109b"></a>Deeply nested **URL** block collapsed for readability.
+
+#### Discovery Consul Access Info HTTP Basic Auth Info Passwd URL Blindfold Secret Info
+
+<a id="deep-6be94c"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery Consul Access Info HTTP Basic Auth Info Passwd URL Clear Secret Info
+
+<a id="deep-82d259"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery Consul Publish Info
+
+A [`publish_info`](#discovery-consul-publish-info) block (within [`discovery_consul`](#discovery-consul)) supports the following:
+
+<a id="discovery-consul-publish-info-disable"></a>&#x2022; [`disable`](#discovery-consul-publish-info-disable) - Optional Block<br>Enable this option
+
+<a id="discovery-consul-publish-info-publish"></a>&#x2022; [`publish`](#discovery-consul-publish-info-publish) - Optional Block<br>Enable this option
+
+#### Discovery K8S
+
+A [`discovery_k8s`](#discovery-k8s) block supports the following:
+
+<a id="discovery-k8s-access-info"></a>&#x2022; [`access_info`](#discovery-k8s-access-info) - Optional Block<br>K8S API Server. K8S API server access<br>See [Access Info](#discovery-k8s-access-info) below.
+
+<a id="discovery-k8s-default-all"></a>&#x2022; [`default_all`](#discovery-k8s-default-all) - Optional Block<br>Enable this option
+
+<a id="discovery-k8s-namespace-mapping"></a>&#x2022; [`namespace_mapping`](#discovery-k8s-namespace-mapping) - Optional Block<br>Select the mapping between K8S namespaces from which services will be discovered and App Namespace to which the discovered services will be shared<br>See [Namespace Mapping](#discovery-k8s-namespace-mapping) below.
+
+<a id="discovery-k8s-publish-info"></a>&#x2022; [`publish_info`](#discovery-k8s-publish-info) - Optional Block<br>VIP Publish Configurations. K8S Configuration to publish VIPs<br>See [Publish Info](#discovery-k8s-publish-info) below.
+
+#### Discovery K8S Access Info
+
+An [`access_info`](#discovery-k8s-access-info) block (within [`discovery_k8s`](#discovery-k8s)) supports the following:
+
+<a id="info-731c25"></a>&#x2022; [`connection_info`](#info-731c25) - Optional Block<br>Configuration details to access discovery service REST API<br>See [Connection Info](#info-731c25) below.
+
+<a id="discovery-k8s-access-info-isolated"></a>&#x2022; [`isolated`](#discovery-k8s-access-info-isolated) - Optional Block<br>Enable this option
+
+<a id="url-d50898"></a>&#x2022; [`kubeconfig_url`](#url-d50898) - Optional Block<br>SecretType is used in an object to indicate a sensitive/confidential field<br>See [Kubeconfig URL](#url-d50898) below.
+
+<a id="discovery-k8s-access-info-reachable"></a>&#x2022; [`reachable`](#discovery-k8s-access-info-reachable) - Optional Block<br>Enable this option
+
+#### Discovery K8S Access Info Connection Info
+
+A [`connection_info`](#info-731c25) block (within [`discovery_k8s.access_info`](#discovery-k8s-access-info)) supports the following:
+
+<a id="server-c32428"></a>&#x2022; [`api_server`](#server-c32428) - Optional String<br>API server must be a fully qualified domain string and port specified as host:port pair
+
+<a id="info-16e7c5"></a>&#x2022; [`tls_info`](#info-16e7c5) - Optional Block<br>TLS config for client of discovery service<br>See [TLS Info](#info-16e7c5) below.
+
+#### Discovery K8S Access Info Connection Info TLS Info
+
+<a id="deep-4a5283"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery K8S Access Info Connection Info TLS Info Key URL
+
+<a id="deep-a976c1"></a>Deeply nested **URL** block collapsed for readability.
+
+#### Discovery K8S Access Info Connection Info TLS Info Key URL Blindfold Secret Info
+
+<a id="deep-c49615"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery K8S Access Info Connection Info TLS Info Key URL Clear Secret Info
+
+<a id="deep-b39c26"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery K8S Access Info Kubeconfig URL
+
+A [`kubeconfig_url`](#url-d50898) block (within [`discovery_k8s.access_info`](#discovery-k8s-access-info)) supports the following:
+
+<a id="info-fef53c"></a>&#x2022; [`blindfold_secret_info`](#info-fef53c) - Optional Block<br>BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-fef53c) below.
+
+<a id="info-ba8969"></a>&#x2022; [`clear_secret_info`](#info-ba8969) - Optional Block<br>ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-ba8969) below.
 
-A [`custom_auth_types`](#custom-auth-types) block supports the following:
+#### Discovery K8S Access Info Kubeconfig URL Blindfold Secret Info
 
-<a id="custom-auth-types-parameter-name"></a>&#x2022; [`parameter_name`](#custom-auth-types-parameter-name) - Optional String<br>The authentication parameter name
+<a id="deep-faaa11"></a>Deeply nested **Info** block collapsed for readability.
 
-<a id="custom-auth-types-parameter-type"></a>&#x2022; [`parameter_type`](#custom-auth-types-parameter-type) - Optional String  Defaults to `QUERY_PARAMETER`<br>Possible values are `QUERY_PARAMETER`, `HEADER`, `COOKIE`<br>[Enum: QUERY_PARAMETER|HEADER|COOKIE] Enumeration for authentication parameter types
+#### Discovery K8S Access Info Kubeconfig URL Clear Secret Info
+
+<a id="deep-4a4f8b"></a>Deeply nested **Info** block collapsed for readability.
+
+#### Discovery K8S Namespace Mapping
+
+A [`namespace_mapping`](#discovery-k8s-namespace-mapping) block (within [`discovery_k8s`](#discovery-k8s)) supports the following:
+
+<a id="discovery-k8s-namespace-mapping-items"></a>&#x2022; [`items`](#discovery-k8s-namespace-mapping-items) - Optional Block<br>Map K8S namespace(s) to App Namespaces. In Shared Configuration, Discovered Services can only be mapped to a single App Namespace, which is determined by the first matched regex<br>See [Items](#discovery-k8s-namespace-mapping-items) below.
+
+#### Discovery K8S Namespace Mapping Items
+
+An [`items`](#discovery-k8s-namespace-mapping-items) block (within [`discovery_k8s.namespace_mapping`](#discovery-k8s-namespace-mapping)) supports the following:
+
+<a id="namespace-b6599c"></a>&#x2022; [`namespace`](#namespace-b6599c) - Optional String<br>F5XC Application Namespaces. Select a namespace
+
+<a id="regex-0aa709"></a>&#x2022; [`namespace_regex`](#regex-0aa709) - Optional String<br>The regex here will be used to match K8S namespace(s)
+
+#### Discovery K8S Publish Info
+
+A [`publish_info`](#discovery-k8s-publish-info) block (within [`discovery_k8s`](#discovery-k8s)) supports the following:
+
+<a id="discovery-k8s-publish-info-disable"></a>&#x2022; [`disable`](#discovery-k8s-publish-info-disable) - Optional Block<br>Enable this option
+
+<a id="delegation-53a235"></a>&#x2022; [`dns_delegation`](#delegation-53a235) - Optional Block<br>K8SDelegationType<br>See [DNS Delegation](#delegation-53a235) below.
+
+<a id="discovery-k8s-publish-info-publish"></a>&#x2022; [`publish`](#discovery-k8s-publish-info-publish) - Optional Block<br>K8SPublishType<br>See [Publish](#discovery-k8s-publish-info-publish) below.
+
+<a id="fqdns-f85bbe"></a>&#x2022; [`publish_fqdns`](#fqdns-f85bbe) - Optional Block<br>Enable this option
+
+#### Discovery K8S Publish Info DNS Delegation
+
+A [`dns_delegation`](#delegation-53a235) block (within [`discovery_k8s.publish_info`](#discovery-k8s-publish-info)) supports the following:
+
+<a id="mode-f08507"></a>&#x2022; [`dns_mode`](#mode-f08507) - Optional String  Defaults to `CORE_DNS`<br>Possible values are `CORE_DNS`, `KUBE_DNS`<br>[Enum: CORE_DNS|KUBE_DNS] Two modes are possible CoreDNS: Whether external K8S cluster is running core-DNS KubeDNS: External K8S cluster is running kube-DNS
+
+<a id="subdomain-f4f8f0"></a>&#x2022; [`subdomain`](#subdomain-f4f8f0) - Optional String<br>The DNS subdomain for which F5XC will respond to DNS queries
+
+#### Discovery K8S Publish Info Publish
+
+A [`publish`](#discovery-k8s-publish-info-publish) block (within [`discovery_k8s.publish_info`](#discovery-k8s-publish-info)) supports the following:
+
+<a id="namespace-a13be9"></a>&#x2022; [`namespace`](#namespace-a13be9) - Optional String<br>The namespace where the service/endpoints need to be created if it's not included in the domain. The external K8S administrator needs to ensure that the namespace exists
 
 #### Timeouts
 
@@ -110,6 +279,88 @@ A [`timeouts`](#timeouts) block supports the following:
 
 <a id="timeouts-update"></a>&#x2022; [`update`](#timeouts-update) - Optional String (Defaults to `10 minutes`)<br>Used when updating the resource
 
+#### Where
+
+A [`where`](#where) block supports the following:
+
+<a id="where-site"></a>&#x2022; [`site`](#where-site) - Optional Block<br>Specifies a direct reference to a site configuration object<br>See [Site](#where-site) below.
+
+<a id="where-virtual-network"></a>&#x2022; [`virtual_network`](#where-virtual-network) - Optional Block<br>Specifies a direct reference to a network configuration object<br>See [Virtual Network](#where-virtual-network) below.
+
+<a id="where-virtual-site"></a>&#x2022; [`virtual_site`](#where-virtual-site) - Optional Block<br>Virtual Site. A reference to virtual_site object<br>See [Virtual Site](#where-virtual-site) below.
+
+#### Where Site
+
+A [`site`](#where-site) block (within [`where`](#where)) supports the following:
+
+<a id="where-site-disable-internet-vip"></a>&#x2022; [`disable_internet_vip`](#where-site-disable-internet-vip) - Optional Block<br>Enable this option
+
+<a id="where-site-enable-internet-vip"></a>&#x2022; [`enable_internet_vip`](#where-site-enable-internet-vip) - Optional Block<br>Enable this option
+
+<a id="where-site-network-type"></a>&#x2022; [`network_type`](#where-site-network-type) - Optional String  Defaults to `VIRTUAL_NETWORK_SITE_LOCAL`<br>Possible values are `VIRTUAL_NETWORK_SITE_LOCAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE`, `VIRTUAL_NETWORK_PER_SITE`, `VIRTUAL_NETWORK_PUBLIC`, `VIRTUAL_NETWORK_GLOBAL`, `VIRTUAL_NETWORK_SITE_SERVICE`, `VIRTUAL_NETWORK_VER_INTERNAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE`, `VIRTUAL_NETWORK_IP_AUTO`, `VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK`, `VIRTUAL_NETWORK_SRV6_NETWORK`, `VIRTUAL_NETWORK_IP_FABRIC`, `VIRTUAL_NETWORK_SEGMENT`<br>[Enum: VIRTUAL_NETWORK_SITE_LOCAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE|VIRTUAL_NETWORK_PER_SITE|VIRTUAL_NETWORK_PUBLIC|VIRTUAL_NETWORK_GLOBAL|VIRTUAL_NETWORK_SITE_SERVICE|VIRTUAL_NETWORK_VER_INTERNAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE|VIRTUAL_NETWORK_IP_AUTO|VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK|VIRTUAL_NETWORK_SRV6_NETWORK|VIRTUAL_NETWORK_IP_FABRIC|VIRTUAL_NETWORK_SEGMENT] Different types of virtual networks understood by the system Virtual-network of type VIRTUAL_NETWORK_SITE_LOCAL provides connectivity to public (outside) network. This is an insecure network and is connected to public internet via NAT Gateways/firwalls Virtual-network of this type is local to
+
+<a id="where-site-ref"></a>&#x2022; [`ref`](#where-site-ref) - Optional Block<br>Reference. A site direct reference<br>See [Ref](#where-site-ref) below.
+
+#### Where Site Ref
+
+A [`ref`](#where-site-ref) block (within [`where.site`](#where-site)) supports the following:
+
+<a id="where-site-ref-kind"></a>&#x2022; [`kind`](#where-site-ref-kind) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="where-site-ref-name"></a>&#x2022; [`name`](#where-site-ref-name) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. Route's) name
+
+<a id="where-site-ref-namespace"></a>&#x2022; [`namespace`](#where-site-ref-namespace) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. Route's) namespace
+
+<a id="where-site-ref-tenant"></a>&#x2022; [`tenant`](#where-site-ref-tenant) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. Route's) tenant
+
+<a id="where-site-ref-uid"></a>&#x2022; [`uid`](#where-site-ref-uid) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. Route's) uid
+
+#### Where Virtual Network
+
+A [`virtual_network`](#where-virtual-network) block (within [`where`](#where)) supports the following:
+
+<a id="where-virtual-network-ref"></a>&#x2022; [`ref`](#where-virtual-network-ref) - Optional Block<br>Virtual network direct reference<br>See [Ref](#where-virtual-network-ref) below.
+
+#### Where Virtual Network Ref
+
+A [`ref`](#where-virtual-network-ref) block (within [`where.virtual_network`](#where-virtual-network)) supports the following:
+
+<a id="where-virtual-network-ref-kind"></a>&#x2022; [`kind`](#where-virtual-network-ref-kind) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="where-virtual-network-ref-name"></a>&#x2022; [`name`](#where-virtual-network-ref-name) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. Route's) name
+
+<a id="where-virtual-network-ref-namespace"></a>&#x2022; [`namespace`](#where-virtual-network-ref-namespace) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. Route's) namespace
+
+<a id="where-virtual-network-ref-tenant"></a>&#x2022; [`tenant`](#where-virtual-network-ref-tenant) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. Route's) tenant
+
+<a id="where-virtual-network-ref-uid"></a>&#x2022; [`uid`](#where-virtual-network-ref-uid) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. Route's) uid
+
+#### Where Virtual Site
+
+A [`virtual_site`](#where-virtual-site) block (within [`where`](#where)) supports the following:
+
+<a id="where-virtual-site-disable-internet-vip"></a>&#x2022; [`disable_internet_vip`](#where-virtual-site-disable-internet-vip) - Optional Block<br>Enable this option
+
+<a id="where-virtual-site-enable-internet-vip"></a>&#x2022; [`enable_internet_vip`](#where-virtual-site-enable-internet-vip) - Optional Block<br>Enable this option
+
+<a id="where-virtual-site-network-type"></a>&#x2022; [`network_type`](#where-virtual-site-network-type) - Optional String  Defaults to `VIRTUAL_NETWORK_SITE_LOCAL`<br>Possible values are `VIRTUAL_NETWORK_SITE_LOCAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE`, `VIRTUAL_NETWORK_PER_SITE`, `VIRTUAL_NETWORK_PUBLIC`, `VIRTUAL_NETWORK_GLOBAL`, `VIRTUAL_NETWORK_SITE_SERVICE`, `VIRTUAL_NETWORK_VER_INTERNAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE`, `VIRTUAL_NETWORK_IP_AUTO`, `VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK`, `VIRTUAL_NETWORK_SRV6_NETWORK`, `VIRTUAL_NETWORK_IP_FABRIC`, `VIRTUAL_NETWORK_SEGMENT`<br>[Enum: VIRTUAL_NETWORK_SITE_LOCAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE|VIRTUAL_NETWORK_PER_SITE|VIRTUAL_NETWORK_PUBLIC|VIRTUAL_NETWORK_GLOBAL|VIRTUAL_NETWORK_SITE_SERVICE|VIRTUAL_NETWORK_VER_INTERNAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE|VIRTUAL_NETWORK_IP_AUTO|VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK|VIRTUAL_NETWORK_SRV6_NETWORK|VIRTUAL_NETWORK_IP_FABRIC|VIRTUAL_NETWORK_SEGMENT] Different types of virtual networks understood by the system Virtual-network of type VIRTUAL_NETWORK_SITE_LOCAL provides connectivity to public (outside) network. This is an insecure network and is connected to public internet via NAT Gateways/firwalls Virtual-network of this type is local to
+
+<a id="where-virtual-site-ref"></a>&#x2022; [`ref`](#where-virtual-site-ref) - Optional Block<br>Virtual_site direct reference<br>See [Ref](#where-virtual-site-ref) below.
+
+#### Where Virtual Site Ref
+
+A [`ref`](#where-virtual-site-ref) block (within [`where.virtual_site`](#where-virtual-site)) supports the following:
+
+<a id="where-virtual-site-ref-kind"></a>&#x2022; [`kind`](#where-virtual-site-ref-kind) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="where-virtual-site-ref-name"></a>&#x2022; [`name`](#where-virtual-site-ref-name) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. Route's) name
+
+<a id="where-virtual-site-ref-namespace"></a>&#x2022; [`namespace`](#where-virtual-site-ref-namespace) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. Route's) namespace
+
+<a id="where-virtual-site-ref-tenant"></a>&#x2022; [`tenant`](#where-virtual-site-ref-tenant) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. Route's) tenant
+
+<a id="where-virtual-site-ref-uid"></a>&#x2022; [`uid`](#where-virtual-site-ref-uid) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. Route's) uid
+
 ---
 
 ## Common Types

package/dist/docs/resources/dns_domain.md

@@ -32,7 +32,7 @@ resource "f5xc_dns_domain" "example" {
   }
 
   # Resource-specific configuration
-  # Can be used for messages where no values are needed.
+  # Enable this option
   volterra_managed {
     # Configure volterra_managed settings
   }
@@ -62,7 +62,7 @@ resource "f5xc_dns_domain" "example" {
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
 
-<a id="volterra-managed"></a>&#x2022; [`volterra_managed`](#volterra-managed) - Optional Block<br>Can be used for messages where no values are needed
+<a id="volterra-managed"></a>&#x2022; [`volterra_managed`](#volterra-managed) - Optional Block<br>Enable this option
 
 ### Attributes Reference
 

package/dist/docs/resources/endpoint.md

@@ -120,7 +120,7 @@ A [`service_selector`](#service-info-service-selector) block (within [`service_i
 
 A [`snat_pool`](#snat-pool) block supports the following:
 
-<a id="snat-pool-no-snat-pool"></a>&#x2022; [`no_snat_pool`](#snat-pool-no-snat-pool) - Optional Block<br>Can be used for messages where no values are needed
+<a id="snat-pool-no-snat-pool"></a>&#x2022; [`no_snat_pool`](#snat-pool-no-snat-pool) - Optional Block<br>Enable this option
 
 <a id="snat-pool-snat-pool"></a>&#x2022; [`snat_pool`](#snat-pool-snat-pool) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Snat Pool](#snat-pool-snat-pool) below.
 
@@ -156,9 +156,9 @@ A [`where`](#where) block supports the following:
 
 A [`site`](#where-site) block (within [`where`](#where)) supports the following:
 
-<a id="where-site-disable-internet-vip"></a>&#x2022; [`disable_internet_vip`](#where-site-disable-internet-vip) - Optional Block<br>Can be used for messages where no values are needed
+<a id="where-site-disable-internet-vip"></a>&#x2022; [`disable_internet_vip`](#where-site-disable-internet-vip) - Optional Block<br>Enable this option
 
-<a id="where-site-enable-internet-vip"></a>&#x2022; [`enable_internet_vip`](#where-site-enable-internet-vip) - Optional Block<br>Can be used for messages where no values are needed
+<a id="where-site-enable-internet-vip"></a>&#x2022; [`enable_internet_vip`](#where-site-enable-internet-vip) - Optional Block<br>Enable this option
 
 <a id="where-site-network-type"></a>&#x2022; [`network_type`](#where-site-network-type) - Optional String  Defaults to `VIRTUAL_NETWORK_SITE_LOCAL`<br>Possible values are `VIRTUAL_NETWORK_SITE_LOCAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE`, `VIRTUAL_NETWORK_PER_SITE`, `VIRTUAL_NETWORK_PUBLIC`, `VIRTUAL_NETWORK_GLOBAL`, `VIRTUAL_NETWORK_SITE_SERVICE`, `VIRTUAL_NETWORK_VER_INTERNAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE`, `VIRTUAL_NETWORK_IP_AUTO`, `VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK`, `VIRTUAL_NETWORK_SRV6_NETWORK`, `VIRTUAL_NETWORK_IP_FABRIC`, `VIRTUAL_NETWORK_SEGMENT`<br>[Enum: VIRTUAL_NETWORK_SITE_LOCAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE|VIRTUAL_NETWORK_PER_SITE|VIRTUAL_NETWORK_PUBLIC|VIRTUAL_NETWORK_GLOBAL|VIRTUAL_NETWORK_SITE_SERVICE|VIRTUAL_NETWORK_VER_INTERNAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE|VIRTUAL_NETWORK_IP_AUTO|VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK|VIRTUAL_NETWORK_SRV6_NETWORK|VIRTUAL_NETWORK_IP_FABRIC|VIRTUAL_NETWORK_SEGMENT] Different types of virtual networks understood by the system Virtual-network of type VIRTUAL_NETWORK_SITE_LOCAL provides connectivity to public (outside) network. This is an insecure network and is connected to public internet via NAT Gateways/firwalls Virtual-network of this type is local to
 
@@ -202,9 +202,9 @@ A [`ref`](#where-virtual-network-ref) block (within [`where.virtual_network`](#w
 
 A [`virtual_site`](#where-virtual-site) block (within [`where`](#where)) supports the following:
 
-<a id="where-virtual-site-disable-internet-vip"></a>&#x2022; [`disable_internet_vip`](#where-virtual-site-disable-internet-vip) - Optional Block<br>Can be used for messages where no values are needed
+<a id="where-virtual-site-disable-internet-vip"></a>&#x2022; [`disable_internet_vip`](#where-virtual-site-disable-internet-vip) - Optional Block<br>Enable this option
 
-<a id="where-virtual-site-enable-internet-vip"></a>&#x2022; [`enable_internet_vip`](#where-virtual-site-enable-internet-vip) - Optional Block<br>Can be used for messages where no values are needed
+<a id="where-virtual-site-enable-internet-vip"></a>&#x2022; [`enable_internet_vip`](#where-virtual-site-enable-internet-vip) - Optional Block<br>Enable this option
 
 <a id="where-virtual-site-network-type"></a>&#x2022; [`network_type`](#where-virtual-site-network-type) - Optional String  Defaults to `VIRTUAL_NETWORK_SITE_LOCAL`<br>Possible values are `VIRTUAL_NETWORK_SITE_LOCAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE`, `VIRTUAL_NETWORK_PER_SITE`, `VIRTUAL_NETWORK_PUBLIC`, `VIRTUAL_NETWORK_GLOBAL`, `VIRTUAL_NETWORK_SITE_SERVICE`, `VIRTUAL_NETWORK_VER_INTERNAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE`, `VIRTUAL_NETWORK_IP_AUTO`, `VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK`, `VIRTUAL_NETWORK_SRV6_NETWORK`, `VIRTUAL_NETWORK_IP_FABRIC`, `VIRTUAL_NETWORK_SEGMENT`<br>[Enum: VIRTUAL_NETWORK_SITE_LOCAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE|VIRTUAL_NETWORK_PER_SITE|VIRTUAL_NETWORK_PUBLIC|VIRTUAL_NETWORK_GLOBAL|VIRTUAL_NETWORK_SITE_SERVICE|VIRTUAL_NETWORK_VER_INTERNAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE|VIRTUAL_NETWORK_IP_AUTO|VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK|VIRTUAL_NETWORK_SRV6_NETWORK|VIRTUAL_NETWORK_IP_FABRIC|VIRTUAL_NETWORK_SEGMENT] Different types of virtual networks understood by the system Virtual-network of type VIRTUAL_NETWORK_SITE_LOCAL provides connectivity to public (outside) network. This is an insecure network and is connected to public internet via NAT Gateways/firwalls Virtual-network of this type is local to