@robinmordasiewicz/f5xc-terraform-mcp 3.5.0 → 3.6.0

package/dist/docs/resources/site_mesh_group.md

@@ -70,9 +70,9 @@ resource "f5xc_site_mesh_group" "example" {
 ### Spec Argument Reference
 
 -> **One of the following:**
-&#x2022; <a id="disable-re-fallback"></a>[`disable_re_fallback`](#disable-re-fallback) - Optional Block<br>Enable this option
+&#x2022; <a id="disable-re-fallback"></a>[`disable_re_fallback`](#disable-re-fallback) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="enable-re-fallback"></a>&#x2022; [`enable_re_fallback`](#enable-re-fallback) - Optional Block<br>Enable this option
+<a id="enable-re-fallback"></a>&#x2022; [`enable_re_fallback`](#enable-re-fallback) - Optional Block<br>Can be used for messages where no values are needed
 
 -> **One of the following:**
 &#x2022; <a id="full-mesh"></a>[`full_mesh`](#full-mesh) - Optional Block<br>Full Mesh. Details of Full Mesh Group Type<br>See [Full Mesh](#full-mesh) below for details.
@@ -81,7 +81,7 @@ resource "f5xc_site_mesh_group" "example" {
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
 
-<a id="virtual-site"></a>&#x2022; [`virtual_site`](#virtual-site) - Optional Block<br>Virtual Site (Sites in this group). Set of sites for which this mesh group config is valid. If 'Type' is Spoke, then it gives set of spoke sites. If 'Type' is Hub, then it gives set of hub sites. If 'Type' is Full Mesh, then it gives set of sites that are connected in full mesh<br>See [Virtual Site](#virtual-site) below for details.
+<a id="virtual-site"></a>&#x2022; [`virtual_site`](#virtual-site) - Optional Block<br>Set of sites for which this mesh group config is valid. If 'Type' is Spoke, then it gives set of spoke sites. If 'Type' is Hub, then it gives set of hub sites<br>See [Virtual Site](#virtual-site) below for details.
 
 ### Attributes Reference
 
@@ -95,37 +95,37 @@ In addition to all arguments above, the following attributes are exported:
 
 A [`full_mesh`](#full-mesh) block supports the following:
 
-<a id="full-mesh-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#full-mesh-control-and-data-plane-mesh) - Optional Block<br>Enable this option
+<a id="full-mesh-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#full-mesh-control-and-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="full-mesh-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#full-mesh-data-plane-mesh) - Optional Block<br>Enable this option
+<a id="full-mesh-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#full-mesh-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
 
 #### Hub Mesh
 
 A [`hub_mesh`](#hub-mesh) block supports the following:
 
-<a id="hub-mesh-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#hub-mesh-control-and-data-plane-mesh) - Optional Block<br>Enable this option
+<a id="hub-mesh-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#hub-mesh-control-and-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="hub-mesh-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#hub-mesh-data-plane-mesh) - Optional Block<br>Enable this option
+<a id="hub-mesh-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#hub-mesh-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
 
 #### Spoke Mesh
 
 A [`spoke_mesh`](#spoke-mesh) block supports the following:
 
-<a id="spoke-mesh-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#spoke-mesh-control-and-data-plane-mesh) - Optional Block<br>Enable this option
+<a id="spoke-mesh-control-and-data-plane-mesh"></a>&#x2022; [`control_and_data_plane_mesh`](#spoke-mesh-control-and-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="spoke-mesh-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#spoke-mesh-data-plane-mesh) - Optional Block<br>Enable this option
+<a id="spoke-mesh-data-plane-mesh"></a>&#x2022; [`data_plane_mesh`](#spoke-mesh-data-plane-mesh) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="spoke-mesh-hub-mesh-group"></a>&#x2022; [`hub_mesh_group`](#spoke-mesh-hub-mesh-group) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Hub Mesh Group](#spoke-mesh-hub-mesh-group) below.
+<a id="spoke-mesh-hub-mesh-group"></a>&#x2022; [`hub_mesh_group`](#spoke-mesh-hub-mesh-group) - Optional Block<br>Type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Hub Mesh Group](#spoke-mesh-hub-mesh-group) below.
 
 #### Spoke Mesh Hub Mesh Group
 
 A [`hub_mesh_group`](#spoke-mesh-hub-mesh-group) block (within [`spoke_mesh`](#spoke-mesh)) supports the following:
 
-<a id="spoke-mesh-hub-mesh-group-name"></a>&#x2022; [`name`](#spoke-mesh-hub-mesh-group-name) - Optional String<br>Name. 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="spoke-mesh-hub-mesh-group-name"></a>&#x2022; [`name`](#spoke-mesh-hub-mesh-group-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="spoke-mesh-hub-mesh-group-namespace"></a>&#x2022; [`namespace`](#spoke-mesh-hub-mesh-group-namespace) - Optional String<br>Namespace. 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="spoke-mesh-hub-mesh-group-namespace"></a>&#x2022; [`namespace`](#spoke-mesh-hub-mesh-group-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="spoke-mesh-hub-mesh-group-tenant"></a>&#x2022; [`tenant`](#spoke-mesh-hub-mesh-group-tenant) - Optional String<br>Tenant. 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="spoke-mesh-hub-mesh-group-tenant"></a>&#x2022; [`tenant`](#spoke-mesh-hub-mesh-group-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
 
 #### Timeouts
 
@@ -143,15 +143,15 @@ A [`timeouts`](#timeouts) block supports the following:
 
 A [`virtual_site`](#virtual-site) block supports the following:
 
-<a id="virtual-site-kind"></a>&#x2022; [`kind`](#virtual-site-kind) - Optional String<br>Kind. 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="virtual-site-kind"></a>&#x2022; [`kind`](#virtual-site-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="virtual-site-name"></a>&#x2022; [`name`](#virtual-site-name) - Optional String<br>Name. 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="virtual-site-name"></a>&#x2022; [`name`](#virtual-site-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="virtual-site-namespace"></a>&#x2022; [`namespace`](#virtual-site-namespace) - Optional String<br>Namespace. 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="virtual-site-namespace"></a>&#x2022; [`namespace`](#virtual-site-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="virtual-site-tenant"></a>&#x2022; [`tenant`](#virtual-site-tenant) - Optional String<br>Tenant. 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="virtual-site-tenant"></a>&#x2022; [`tenant`](#virtual-site-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="virtual-site-uid"></a>&#x2022; [`uid`](#virtual-site-uid) - Optional String<br>UID. 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
+<a id="virtual-site-uid"></a>&#x2022; [`uid`](#virtual-site-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
 
 ---
 

package/dist/docs/resources/subnet.md

@@ -36,11 +36,11 @@ resource "f5xc_subnet" "example" {
   connect_to_layer2 {
     # Configure connect_to_layer2 settings
   }
-  # Object reference. This type establishes a direct referenc...
+  # Type establishes a direct reference from one object(the r...
   layer2_intf_ref {
     # Configure layer2_intf_ref settings
   }
-  # Enable this option
+  # Can be used for messages where no values are needed.
   connect_to_slo {
     # Configure connect_to_slo settings
   }
@@ -68,10 +68,10 @@ resource "f5xc_subnet" "example" {
 
 -> **One of the following:**
 &#x2022; <a id="connect-to-layer2"></a>[`connect_to_layer2`](#connect-to-layer2) - Optional Block<br>Subnet connection to Layer2 Interface<br>See [Connect To Layer2](#connect-to-layer2) below for details.
-<br><br>&#x2022; <a id="connect-to-slo"></a>[`connect_to_slo`](#connect-to-slo) - Optional Block<br>Enable this option
-<br><br>&#x2022; <a id="isolated-nw"></a>[`isolated_nw`](#isolated-nw) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="connect-to-slo"></a>[`connect_to_slo`](#connect-to-slo) - Optional Block<br>Can be used for messages where no values are needed
+<br><br>&#x2022; <a id="isolated-nw"></a>[`isolated_nw`](#isolated-nw) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="site-subnet-params"></a>&#x2022; [`site_subnet_params`](#site-subnet-params) - Optional Block<br>Site Subnet Parameters. Configure subnet parameters per site<br>See [Site Subnet Params](#site-subnet-params) below for details.
+<a id="site-subnet-params"></a>&#x2022; [`site_subnet_params`](#site-subnet-params) - Optional Block<br>Configure subnet parameters per site<br>See [Site Subnet Params](#site-subnet-params) below for details.
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
 
@@ -87,45 +87,45 @@ In addition to all arguments above, the following attributes are exported:
 
 A [`connect_to_layer2`](#connect-to-layer2) block supports the following:
 
-<a id="connect-to-layer2-layer2-intf-ref"></a>&#x2022; [`layer2_intf_ref`](#connect-to-layer2-layer2-intf-ref) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Layer2 Intf Ref](#connect-to-layer2-layer2-intf-ref) below.
+<a id="connect-to-layer2-layer2-intf-ref"></a>&#x2022; [`layer2_intf_ref`](#connect-to-layer2-layer2-intf-ref) - Optional Block<br>Type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Layer2 Intf Ref](#connect-to-layer2-layer2-intf-ref) below.
 
 #### Connect To Layer2 Layer2 Intf Ref
 
 A [`layer2_intf_ref`](#connect-to-layer2-layer2-intf-ref) block (within [`connect_to_layer2`](#connect-to-layer2)) supports the following:
 
-<a id="connect-to-layer2-layer2-intf-ref-name"></a>&#x2022; [`name`](#connect-to-layer2-layer2-intf-ref-name) - Optional String<br>Name. 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="connect-to-layer2-layer2-intf-ref-name"></a>&#x2022; [`name`](#connect-to-layer2-layer2-intf-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="namespace-afda4a"></a>&#x2022; [`namespace`](#namespace-afda4a) - Optional String<br>Namespace. 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="namespace-afda4a"></a>&#x2022; [`namespace`](#namespace-afda4a) - 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="tenant-0fab0d"></a>&#x2022; [`tenant`](#tenant-0fab0d) - Optional String<br>Tenant. 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="tenant-0fab0d"></a>&#x2022; [`tenant`](#tenant-0fab0d) - 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
 
 #### Site Subnet Params
 
 A [`site_subnet_params`](#site-subnet-params) block supports the following:
 
-<a id="site-subnet-params-dhcp"></a>&#x2022; [`dhcp`](#site-subnet-params-dhcp) - Optional Block<br>Enable this option
+<a id="site-subnet-params-dhcp"></a>&#x2022; [`dhcp`](#site-subnet-params-dhcp) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="site-subnet-params-site"></a>&#x2022; [`site`](#site-subnet-params-site) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Site](#site-subnet-params-site) below.
+<a id="site-subnet-params-site"></a>&#x2022; [`site`](#site-subnet-params-site) - Optional Block<br>Type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Site](#site-subnet-params-site) below.
 
-<a id="site-subnet-params-static-ip"></a>&#x2022; [`static_ip`](#site-subnet-params-static-ip) - Optional Block<br>Enable this option
+<a id="site-subnet-params-static-ip"></a>&#x2022; [`static_ip`](#site-subnet-params-static-ip) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="params-2a5102"></a>&#x2022; [`subnet_dhcp_server_params`](#params-2a5102) - Optional Block<br>Subnet DHCP parameters. Subnet DHCP parameters will be a subset of network_interface.dhcpserverparameterstype as all features in network_interface.dhcpserverparameterstype may not be supported in a subnet<br>See [Subnet DHCP Server Params](#params-2a5102) below.
+<a id="params-2a5102"></a>&#x2022; [`subnet_dhcp_server_params`](#params-2a5102) - Optional Block<br>Subnet DHCP parameters will be a subset of network_interface.dhcpserverparameterstype as all features in network_interface.dhcpserverparameterstype may not be supported in a subnet<br>See [Subnet DHCP Server Params](#params-2a5102) below.
 
 #### Site Subnet Params Site
 
 A [`site`](#site-subnet-params-site) block (within [`site_subnet_params`](#site-subnet-params)) supports the following:
 
-<a id="site-subnet-params-site-name"></a>&#x2022; [`name`](#site-subnet-params-site-name) - Optional String<br>Name. 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="site-subnet-params-site-name"></a>&#x2022; [`name`](#site-subnet-params-site-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="site-subnet-params-site-namespace"></a>&#x2022; [`namespace`](#site-subnet-params-site-namespace) - Optional String<br>Namespace. 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="site-subnet-params-site-namespace"></a>&#x2022; [`namespace`](#site-subnet-params-site-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="site-subnet-params-site-tenant"></a>&#x2022; [`tenant`](#site-subnet-params-site-tenant) - Optional String<br>Tenant. 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="site-subnet-params-site-tenant"></a>&#x2022; [`tenant`](#site-subnet-params-site-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
 
 #### Site Subnet Params Subnet DHCP Server Params
 
 A [`subnet_dhcp_server_params`](#params-2a5102) block (within [`site_subnet_params`](#site-subnet-params)) supports the following:
 
-<a id="networks-b234bf"></a>&#x2022; [`dhcp_networks`](#networks-b234bf) - Optional Block<br>Subnet DHCP Networks. List of networks from which DHCP server can allocate IP addresses<br>See [DHCP Networks](#networks-b234bf) below.
+<a id="networks-b234bf"></a>&#x2022; [`dhcp_networks`](#networks-b234bf) - Optional Block<br>List of networks from which DHCP server can allocate IP addresses<br>See [DHCP Networks](#networks-b234bf) below.
 
 #### Site Subnet Params Subnet DHCP Server Params DHCP Networks