@robinmordasiewicz/f5xc-terraform-mcp 3.5.0 → 3.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +283 -104
- package/dist/docs/data-sources/bgp.md +2 -2
- package/dist/docs/data-sources/discovery.md +2 -2
- package/dist/docs/data-sources/fast_acl.md +2 -2
- package/dist/docs/data-sources/fast_acl_rule.md +2 -2
- package/dist/docs/data-sources/irule.md +2 -2
- package/dist/docs/data-sources/log_receiver.md +2 -2
- package/dist/docs/data-sources/network_policy.md +2 -2
- package/dist/docs/data-sources/route.md +2 -2
- package/dist/docs/data-sources/site.md +2 -2
- package/dist/docs/resources/address_allocator.md +7 -7
- package/dist/docs/resources/advertise_policy.md +57 -57
- package/dist/docs/resources/alert_policy.md +40 -40
- package/dist/docs/resources/alert_receiver.md +57 -57
- package/dist/docs/resources/api_crawler.md +13 -13
- package/dist/docs/resources/api_definition.md +11 -11
- package/dist/docs/resources/api_discovery.md +4 -4
- package/dist/docs/resources/api_testing.md +27 -27
- package/dist/docs/resources/apm.md +40 -40
- package/dist/docs/resources/app_api_group.md +20 -20
- package/dist/docs/resources/app_firewall.md +50 -50
- package/dist/docs/resources/app_setting.md +19 -19
- package/dist/docs/resources/app_type.md +7 -7
- package/dist/docs/resources/authentication.md +29 -29
- package/dist/docs/resources/aws_tgw_site.md +140 -140
- package/dist/docs/resources/aws_vpc_site.md +174 -174
- package/dist/docs/resources/azure_vnet_site.md +245 -245
- package/dist/docs/resources/bgp.md +37 -205
- package/dist/docs/resources/bgp_asn_set.md +1 -1
- package/dist/docs/resources/bgp_routing_policy.md +19 -19
- package/dist/docs/resources/bot_defense_app_infrastructure.md +12 -12
- package/dist/docs/resources/cdn_cache_rule.md +5 -5
- package/dist/docs/resources/cdn_loadbalancer.md +418 -418
- package/dist/docs/resources/certificate.md +1 -1
- package/dist/docs/resources/certificate_chain.md +1 -1
- package/dist/docs/resources/cloud_connect.md +28 -28
- package/dist/docs/resources/cloud_credentials.md +35 -35
- package/dist/docs/resources/cloud_elastic_ip.md +8 -8
- package/dist/docs/resources/cloud_link.md +36 -36
- package/dist/docs/resources/cluster.md +86 -86
- package/dist/docs/resources/cminstance.md +22 -22
- package/dist/docs/resources/code_base_integration.md +24 -24
- package/dist/docs/resources/container_registry.md +13 -13
- package/dist/docs/resources/crl.md +1 -1
- package/dist/docs/resources/data_type.md +16 -16
- package/dist/docs/resources/dc_cluster_group.md +4 -4
- package/dist/docs/resources/discovery.md +8 -259
- package/dist/docs/resources/dns_compliance_checks.md +1 -1
- package/dist/docs/resources/dns_domain.md +3 -3
- package/dist/docs/resources/endpoint.md +44 -44
- package/dist/docs/resources/enhanced_firewall_policy.md +51 -51
- package/dist/docs/resources/external_connector.md +42 -42
- package/dist/docs/resources/fast_acl.md +60 -166
- package/dist/docs/resources/fast_acl_rule.md +28 -28
- package/dist/docs/resources/filter_set.md +10 -10
- package/dist/docs/resources/fleet.md +160 -160
- package/dist/docs/resources/forward_proxy_policy.md +82 -82
- package/dist/docs/resources/forwarding_class.md +14 -14
- package/dist/docs/resources/gcp_vpc_site.md +152 -152
- package/dist/docs/resources/global_log_receiver.md +238 -238
- package/dist/docs/resources/healthcheck.md +17 -17
- package/dist/docs/resources/http_loadbalancer.md +1003 -1003
- package/dist/docs/resources/irule.md +5 -7
- package/dist/docs/resources/log_receiver.md +825 -44
- package/dist/docs/resources/malicious_user_mitigation.md +10 -10
- package/dist/docs/resources/nat_policy.md +86 -86
- package/dist/docs/resources/network_connector.md +31 -31
- package/dist/docs/resources/network_firewall.md +22 -22
- package/dist/docs/resources/network_interface.md +77 -77
- package/dist/docs/resources/network_policy.md +38 -217
- package/dist/docs/resources/network_policy_rule.md +21 -21
- package/dist/docs/resources/network_policy_view.md +65 -65
- package/dist/docs/resources/nfv_service.md +76 -76
- package/dist/docs/resources/nginx_service_discovery.md +10 -10
- package/dist/docs/resources/origin_pool.md +166 -166
- package/dist/docs/resources/policer.md +4 -4
- package/dist/docs/resources/policy_based_routing.md +28 -28
- package/dist/docs/resources/protocol_inspection.md +12 -12
- package/dist/docs/resources/protocol_policer.md +14 -14
- package/dist/docs/resources/proxy.md +111 -111
- package/dist/docs/resources/rate_limiter.md +15 -15
- package/dist/docs/resources/rate_limiter_policy.md +56 -56
- package/dist/docs/resources/route.md +183 -183
- package/dist/docs/resources/secret_management_access.md +68 -68
- package/dist/docs/resources/securemesh_site.md +1619 -258
- package/dist/docs/resources/segment.md +4 -4
- package/dist/docs/resources/sensitive_data_policy.md +9 -9
- package/dist/docs/resources/service_policy.md +175 -175
- package/dist/docs/resources/service_policy_rule.md +142 -142
- package/dist/docs/resources/site.md +381 -303
- package/dist/docs/resources/site_mesh_group.md +18 -18
- package/dist/docs/resources/subnet.md +17 -17
- package/dist/docs/resources/tcp_loadbalancer.md +130 -130
- package/dist/docs/resources/tenant_configuration.md +10 -10
- package/dist/docs/resources/trusted_ca_list.md +1 -1
- package/dist/docs/resources/tunnel.md +36 -36
- package/dist/docs/resources/udp_loadbalancer.md +59 -59
- package/dist/docs/resources/usb_policy.md +6 -6
- package/dist/docs/resources/user_identification.md +16 -16
- package/dist/docs/resources/virtual_host.md +225 -225
- package/dist/docs/resources/virtual_network.md +14 -14
- package/dist/docs/resources/virtual_site.md +3 -3
- package/dist/docs/resources/voltstack_site.md +141 -141
- package/dist/docs/resources/waf_exclusion_policy.md +17 -17
- package/dist/docs/resources/workload.md +327 -327
- package/dist/docs/resources/workload_flavor.md +3 -3
- package/dist/metadata/resource-metadata.json +1484 -942
- package/dist/types.d.ts +11 -0
- package/dist/types.d.ts.map +1 -1
- package/dist/types.js.map +1 -1
- package/package.json +1 -1
|
@@ -64,7 +64,7 @@ resource "f5xc_malicious_user_mitigation" "example" {
|
|
|
64
64
|
|
|
65
65
|
### Spec Argument Reference
|
|
66
66
|
|
|
67
|
-
<a id="mitigation-type"></a>• [`mitigation_type`](#mitigation-type) - Optional Block<br>
|
|
67
|
+
<a id="mitigation-type"></a>• [`mitigation_type`](#mitigation-type) - Optional Block<br>Settings that specify the actions to be taken when malicious users are determined to be at different threat levels. User's activity is monitored and continuously analyzed for malicious behavior. From this analysis, a threat-level is assigned to each user<br>See [Mitigation Type](#mitigation-type) below for details.
|
|
68
68
|
|
|
69
69
|
<a id="timeouts"></a>• [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
|
|
70
70
|
|
|
@@ -80,35 +80,35 @@ In addition to all arguments above, the following attributes are exported:
|
|
|
80
80
|
|
|
81
81
|
A [`mitigation_type`](#mitigation-type) block supports the following:
|
|
82
82
|
|
|
83
|
-
<a id="mitigation-type-rules"></a>• [`rules`](#mitigation-type-rules) - Optional Block<br>
|
|
83
|
+
<a id="mitigation-type-rules"></a>• [`rules`](#mitigation-type-rules) - Optional Block<br>Define the threat levels and the corresponding mitigation actions to be taken<br>See [Rules](#mitigation-type-rules) below.
|
|
84
84
|
|
|
85
85
|
#### Mitigation Type Rules
|
|
86
86
|
|
|
87
87
|
A [`rules`](#mitigation-type-rules) block (within [`mitigation_type`](#mitigation-type)) supports the following:
|
|
88
88
|
|
|
89
|
-
<a id="mitigation-type-rules-mitigation-action"></a>• [`mitigation_action`](#mitigation-type-rules-mitigation-action) - Optional Block<br>
|
|
89
|
+
<a id="mitigation-type-rules-mitigation-action"></a>• [`mitigation_action`](#mitigation-type-rules-mitigation-action) - Optional Block<br>Supported actions that can be taken to mitigate malicious activity from a user<br>See [Mitigation Action](#mitigation-type-rules-mitigation-action) below.
|
|
90
90
|
|
|
91
|
-
<a id="mitigation-type-rules-threat-level"></a>• [`threat_level`](#mitigation-type-rules-threat-level) - Optional Block<br>
|
|
91
|
+
<a id="mitigation-type-rules-threat-level"></a>• [`threat_level`](#mitigation-type-rules-threat-level) - Optional Block<br>Threat level estimated for each user based on the user's activity and reputation<br>See [Threat Level](#mitigation-type-rules-threat-level) below.
|
|
92
92
|
|
|
93
93
|
#### Mitigation Type Rules Mitigation Action
|
|
94
94
|
|
|
95
95
|
A [`mitigation_action`](#mitigation-type-rules-mitigation-action) block (within [`mitigation_type.rules`](#mitigation-type-rules)) supports the following:
|
|
96
96
|
|
|
97
|
-
<a id="temporarily-ae6df1"></a>• [`block_temporarily`](#temporarily-ae6df1) - Optional Block<br>
|
|
97
|
+
<a id="temporarily-ae6df1"></a>• [`block_temporarily`](#temporarily-ae6df1) - Optional Block<br>Can be used for messages where no values are needed
|
|
98
98
|
|
|
99
|
-
<a id="challenge-783e81"></a>• [`captcha_challenge`](#challenge-783e81) - Optional Block<br>
|
|
99
|
+
<a id="challenge-783e81"></a>• [`captcha_challenge`](#challenge-783e81) - Optional Block<br>Can be used for messages where no values are needed
|
|
100
100
|
|
|
101
|
-
<a id="challenge-784169"></a>• [`javascript_challenge`](#challenge-784169) - Optional Block<br>
|
|
101
|
+
<a id="challenge-784169"></a>• [`javascript_challenge`](#challenge-784169) - Optional Block<br>Can be used for messages where no values are needed
|
|
102
102
|
|
|
103
103
|
#### Mitigation Type Rules Threat Level
|
|
104
104
|
|
|
105
105
|
A [`threat_level`](#mitigation-type-rules-threat-level) block (within [`mitigation_type.rules`](#mitigation-type-rules)) supports the following:
|
|
106
106
|
|
|
107
|
-
<a id="mitigation-type-rules-threat-level-high"></a>• [`high`](#mitigation-type-rules-threat-level-high) - Optional Block<br>
|
|
107
|
+
<a id="mitigation-type-rules-threat-level-high"></a>• [`high`](#mitigation-type-rules-threat-level-high) - Optional Block<br>Can be used for messages where no values are needed
|
|
108
108
|
|
|
109
|
-
<a id="mitigation-type-rules-threat-level-low"></a>• [`low`](#mitigation-type-rules-threat-level-low) - Optional Block<br>
|
|
109
|
+
<a id="mitigation-type-rules-threat-level-low"></a>• [`low`](#mitigation-type-rules-threat-level-low) - Optional Block<br>Can be used for messages where no values are needed
|
|
110
110
|
|
|
111
|
-
<a id="medium-bfd9e9"></a>• [`medium`](#medium-bfd9e9) - Optional Block<br>
|
|
111
|
+
<a id="medium-bfd9e9"></a>• [`medium`](#medium-bfd9e9) - Optional Block<br>Can be used for messages where no values are needed
|
|
112
112
|
|
|
113
113
|
#### Timeouts
|
|
114
114
|
|
|
@@ -32,11 +32,11 @@ resource "f5xc_nat_policy" "example" {
|
|
|
32
32
|
}
|
|
33
33
|
|
|
34
34
|
# Resource-specific configuration
|
|
35
|
-
#
|
|
35
|
+
# List of rules to apply under the NAT Policy. Rule that ma...
|
|
36
36
|
rules {
|
|
37
37
|
# Configure rules settings
|
|
38
38
|
}
|
|
39
|
-
# Action
|
|
39
|
+
# Action to apply on the packet if the NAT rule is applied.
|
|
40
40
|
action {
|
|
41
41
|
# Configure action settings
|
|
42
42
|
}
|
|
@@ -66,7 +66,7 @@ resource "f5xc_nat_policy" "example" {
|
|
|
66
66
|
|
|
67
67
|
### Spec Argument Reference
|
|
68
68
|
|
|
69
|
-
<a id="rules"></a>• [`rules`](#rules) - Optional Block<br>
|
|
69
|
+
<a id="rules"></a>• [`rules`](#rules) - Optional Block<br>List of rules to apply under the NAT Policy. Rule that matches first would be applied<br>See [Rules](#rules) below for details.
|
|
70
70
|
|
|
71
71
|
<a id="site"></a>• [`site`](#site) - Optional Block<br>Site Reference Type. Reference to Site Object<br>See [Site](#site) below for details.
|
|
72
72
|
|
|
@@ -84,15 +84,15 @@ In addition to all arguments above, the following attributes are exported:
|
|
|
84
84
|
|
|
85
85
|
A [`rules`](#rules) block supports the following:
|
|
86
86
|
|
|
87
|
-
<a id="rules-action"></a>• [`action`](#rules-action) - Optional Block<br>Action
|
|
87
|
+
<a id="rules-action"></a>• [`action`](#rules-action) - Optional Block<br>Action to apply on the packet if the NAT rule is applied<br>See [Action](#rules-action) below.
|
|
88
88
|
|
|
89
89
|
<a id="rules-cloud-connect"></a>• [`cloud_connect`](#rules-cloud-connect) - Optional Block<br>Cloud Connect Reference Type. Reference to Cloud connect Object<br>See [Cloud Connect](#rules-cloud-connect) below.
|
|
90
90
|
|
|
91
|
-
<a id="rules-criteria"></a>• [`criteria`](#rules-criteria) - Optional Block<br>Match
|
|
91
|
+
<a id="rules-criteria"></a>• [`criteria`](#rules-criteria) - Optional Block<br>Match criteria of the packet to apply the NAT Rule<br>See [Criteria](#rules-criteria) below.
|
|
92
92
|
|
|
93
|
-
<a id="rules-disable"></a>• [`disable`](#rules-disable) - Optional Block<br>
|
|
93
|
+
<a id="rules-disable"></a>• [`disable`](#rules-disable) - Optional Block<br>Can be used for messages where no values are needed
|
|
94
94
|
|
|
95
|
-
<a id="rules-enable"></a>• [`enable`](#rules-enable) - Optional Block<br>
|
|
95
|
+
<a id="rules-enable"></a>• [`enable`](#rules-enable) - Optional Block<br>Can be used for messages where no values are needed
|
|
96
96
|
|
|
97
97
|
<a id="rules-name"></a>• [`name`](#rules-name) - Optional String<br>Name. Name of the Rule
|
|
98
98
|
|
|
@@ -100,7 +100,7 @@ A [`rules`](#rules) block supports the following:
|
|
|
100
100
|
|
|
101
101
|
<a id="rules-segment"></a>• [`segment`](#rules-segment) - Optional Block<br>Segment Reference Type. Reference to Segment Object<br>See [Segment](#rules-segment) below.
|
|
102
102
|
|
|
103
|
-
<a id="rules-virtual-network"></a>• [`virtual_network`](#rules-virtual-network) - Optional Block<br>
|
|
103
|
+
<a id="rules-virtual-network"></a>• [`virtual_network`](#rules-virtual-network) - Optional Block<br>Carries the reference to virtual network<br>See [Virtual Network](#rules-virtual-network) below.
|
|
104
104
|
|
|
105
105
|
#### Rules Action
|
|
106
106
|
|
|
@@ -108,73 +108,73 @@ An [`action`](#rules-action) block (within [`rules`](#rules)) supports the follo
|
|
|
108
108
|
|
|
109
109
|
<a id="rules-action-dynamic"></a>• [`dynamic`](#rules-action-dynamic) - Optional Block<br>Dynamic Pool. Dynamic Pool Configuration<br>See [Dynamic](#rules-action-dynamic) below.
|
|
110
110
|
|
|
111
|
-
<a id="rules-action-virtual-cidr"></a>• [`virtual_cidr`](#rules-action-virtual-cidr) - Optional String<br>Virtual Subnet NAT
|
|
111
|
+
<a id="rules-action-virtual-cidr"></a>• [`virtual_cidr`](#rules-action-virtual-cidr) - Optional String<br>Virtual Subnet NAT is static NAT that does a one-to-one translation between the real source IP CIDR in the policy and the virtual CIDR in a bidirectional fashion. The range of the real CIDR and virtual CIDRs should be the same (e.g. If the real CIDR has the CIDR
|
|
112
112
|
|
|
113
113
|
#### Rules Action Dynamic
|
|
114
114
|
|
|
115
115
|
A [`dynamic`](#rules-action-dynamic) block (within [`rules.action`](#rules-action)) supports the following:
|
|
116
116
|
|
|
117
|
-
<a id="rules-action-dynamic-elastic-ips"></a>• [`elastic_ips`](#rules-action-dynamic-elastic-ips) - Optional Block<br>
|
|
117
|
+
<a id="rules-action-dynamic-elastic-ips"></a>• [`elastic_ips`](#rules-action-dynamic-elastic-ips) - Optional Block<br>List of references to Cloud Elastic IP Object<br>See [Elastic Ips](#rules-action-dynamic-elastic-ips) below.
|
|
118
118
|
|
|
119
|
-
<a id="rules-action-dynamic-pools"></a>• [`pools`](#rules-action-dynamic-pools) - Optional Block<br>
|
|
119
|
+
<a id="rules-action-dynamic-pools"></a>• [`pools`](#rules-action-dynamic-pools) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Pools](#rules-action-dynamic-pools) below.
|
|
120
120
|
|
|
121
121
|
#### Rules Action Dynamic Elastic Ips
|
|
122
122
|
|
|
123
123
|
An [`elastic_ips`](#rules-action-dynamic-elastic-ips) block (within [`rules.action.dynamic`](#rules-action-dynamic)) supports the following:
|
|
124
124
|
|
|
125
|
-
<a id="rules-action-dynamic-elastic-ips-refs"></a>• [`refs`](#rules-action-dynamic-elastic-ips-refs) - Optional Block<br>
|
|
125
|
+
<a id="rules-action-dynamic-elastic-ips-refs"></a>• [`refs`](#rules-action-dynamic-elastic-ips-refs) - Optional Block<br>Reference to one or more cloud elastic IP objects<br>See [Refs](#rules-action-dynamic-elastic-ips-refs) below.
|
|
126
126
|
|
|
127
127
|
#### Rules Action Dynamic Elastic Ips Refs
|
|
128
128
|
|
|
129
129
|
A [`refs`](#rules-action-dynamic-elastic-ips-refs) block (within [`rules.action.dynamic.elastic_ips`](#rules-action-dynamic-elastic-ips)) supports the following:
|
|
130
130
|
|
|
131
|
-
<a id="kind-df4674"></a>• [`kind`](#kind-df4674) - Optional String<br>
|
|
131
|
+
<a id="kind-df4674"></a>• [`kind`](#kind-df4674) - 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')
|
|
132
132
|
|
|
133
|
-
<a id="name-fdfa81"></a>• [`name`](#name-fdfa81) - Optional String<br>
|
|
133
|
+
<a id="name-fdfa81"></a>• [`name`](#name-fdfa81) - 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
|
|
134
134
|
|
|
135
|
-
<a id="namespace-fa1e70"></a>• [`namespace`](#namespace-fa1e70) - Optional String<br>
|
|
135
|
+
<a id="namespace-fa1e70"></a>• [`namespace`](#namespace-fa1e70) - 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
|
|
136
136
|
|
|
137
|
-
<a id="tenant-aec1f4"></a>• [`tenant`](#tenant-aec1f4) - Optional String<br>
|
|
137
|
+
<a id="tenant-aec1f4"></a>• [`tenant`](#tenant-aec1f4) - 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
|
|
138
138
|
|
|
139
|
-
<a id="uid-83b949"></a>• [`uid`](#uid-83b949) - Optional String<br>
|
|
139
|
+
<a id="uid-83b949"></a>• [`uid`](#uid-83b949) - 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
|
|
140
140
|
|
|
141
141
|
#### Rules Action Dynamic Pools
|
|
142
142
|
|
|
143
143
|
A [`pools`](#rules-action-dynamic-pools) block (within [`rules.action.dynamic`](#rules-action-dynamic)) supports the following:
|
|
144
144
|
|
|
145
|
-
<a id="rules-action-dynamic-pools-prefixes"></a>• [`prefixes`](#rules-action-dynamic-pools-prefixes) - Optional List<br>
|
|
145
|
+
<a id="rules-action-dynamic-pools-prefixes"></a>• [`prefixes`](#rules-action-dynamic-pools-prefixes) - Optional List<br>List of IPv4 prefixes that represent an endpoint
|
|
146
146
|
|
|
147
147
|
#### Rules Cloud Connect
|
|
148
148
|
|
|
149
149
|
A [`cloud_connect`](#rules-cloud-connect) block (within [`rules`](#rules)) supports the following:
|
|
150
150
|
|
|
151
|
-
<a id="rules-cloud-connect-refs"></a>• [`refs`](#rules-cloud-connect-refs) - Optional Block<br>
|
|
151
|
+
<a id="rules-cloud-connect-refs"></a>• [`refs`](#rules-cloud-connect-refs) - Optional Block<br>Reference to Cloud Connect Object<br>See [Refs](#rules-cloud-connect-refs) below.
|
|
152
152
|
|
|
153
153
|
#### Rules Cloud Connect Refs
|
|
154
154
|
|
|
155
155
|
A [`refs`](#rules-cloud-connect-refs) block (within [`rules.cloud_connect`](#rules-cloud-connect)) supports the following:
|
|
156
156
|
|
|
157
|
-
<a id="rules-cloud-connect-refs-kind"></a>• [`kind`](#rules-cloud-connect-refs-kind) - Optional String<br>
|
|
157
|
+
<a id="rules-cloud-connect-refs-kind"></a>• [`kind`](#rules-cloud-connect-refs-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')
|
|
158
158
|
|
|
159
|
-
<a id="rules-cloud-connect-refs-name"></a>• [`name`](#rules-cloud-connect-refs-name) - Optional String<br>
|
|
159
|
+
<a id="rules-cloud-connect-refs-name"></a>• [`name`](#rules-cloud-connect-refs-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
|
|
160
160
|
|
|
161
|
-
<a id="rules-cloud-connect-refs-namespace"></a>• [`namespace`](#rules-cloud-connect-refs-namespace) - Optional String<br>
|
|
161
|
+
<a id="rules-cloud-connect-refs-namespace"></a>• [`namespace`](#rules-cloud-connect-refs-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
|
|
162
162
|
|
|
163
|
-
<a id="rules-cloud-connect-refs-tenant"></a>• [`tenant`](#rules-cloud-connect-refs-tenant) - Optional String<br>
|
|
163
|
+
<a id="rules-cloud-connect-refs-tenant"></a>• [`tenant`](#rules-cloud-connect-refs-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
|
|
164
164
|
|
|
165
|
-
<a id="rules-cloud-connect-refs-uid"></a>• [`uid`](#rules-cloud-connect-refs-uid) - Optional String<br>
|
|
165
|
+
<a id="rules-cloud-connect-refs-uid"></a>• [`uid`](#rules-cloud-connect-refs-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
|
|
166
166
|
|
|
167
167
|
#### Rules Criteria
|
|
168
168
|
|
|
169
169
|
A [`criteria`](#rules-criteria) block (within [`rules`](#rules)) supports the following:
|
|
170
170
|
|
|
171
|
-
<a id="rules-criteria-any"></a>• [`any`](#rules-criteria-any) - Optional Block<br>
|
|
171
|
+
<a id="rules-criteria-any"></a>• [`any`](#rules-criteria-any) - Optional Block<br>Can be used for messages where no values are needed
|
|
172
172
|
|
|
173
173
|
<a id="rules-criteria-destination-cidr"></a>• [`destination_cidr`](#rules-criteria-destination-cidr) - Optional List<br>Destination IP. Destination IP of the packet to match
|
|
174
174
|
|
|
175
|
-
<a id="rules-criteria-destination-port"></a>• [`destination_port`](#rules-criteria-destination-port) - Optional Block<br>Port
|
|
175
|
+
<a id="rules-criteria-destination-port"></a>• [`destination_port`](#rules-criteria-destination-port) - Optional Block<br>Port match of the request can be a range or a specific port<br>See [Destination Port](#rules-criteria-destination-port) below.
|
|
176
176
|
|
|
177
|
-
<a id="rules-criteria-icmp"></a>• [`icmp`](#rules-criteria-icmp) - Optional Block<br>
|
|
177
|
+
<a id="rules-criteria-icmp"></a>• [`icmp`](#rules-criteria-icmp) - Optional Block<br>Can be used for messages where no values are needed
|
|
178
178
|
|
|
179
179
|
<a id="rules-criteria-protocol"></a>• [`protocol`](#rules-criteria-protocol) - Optional String Defaults to `ALL`<br>Possible values are `ALL`, `ICMP`, `TCP`, `UDP`<br>[Enum: ALL|ICMP|TCP|UDP] Protocols. Protocols like TCP, UDP
|
|
180
180
|
|
|
@@ -182,109 +182,109 @@ A [`criteria`](#rules-criteria) block (within [`rules`](#rules)) supports the fo
|
|
|
182
182
|
|
|
183
183
|
<a id="rules-criteria-source-cidr"></a>• [`source_cidr`](#rules-criteria-source-cidr) - Optional List<br>Source IP. Source IP of the packet to match
|
|
184
184
|
|
|
185
|
-
<a id="rules-criteria-source-port"></a>• [`source_port`](#rules-criteria-source-port) - Optional Block<br>Port
|
|
185
|
+
<a id="rules-criteria-source-port"></a>• [`source_port`](#rules-criteria-source-port) - Optional Block<br>Port match of the request can be a range or a specific port<br>See [Source Port](#rules-criteria-source-port) below.
|
|
186
186
|
|
|
187
|
-
<a id="rules-criteria-tcp"></a>• [`tcp`](#rules-criteria-tcp) - Optional Block<br>
|
|
187
|
+
<a id="rules-criteria-tcp"></a>• [`tcp`](#rules-criteria-tcp) - Optional Block<br>Action to apply on the packet if the NAT rule is applied<br>See [TCP](#rules-criteria-tcp) below.
|
|
188
188
|
|
|
189
|
-
<a id="rules-criteria-udp"></a>• [`udp`](#rules-criteria-udp) - Optional Block<br>
|
|
189
|
+
<a id="rules-criteria-udp"></a>• [`udp`](#rules-criteria-udp) - Optional Block<br>Action to apply on the packet if the NAT rule is applied<br>See [UDP](#rules-criteria-udp) below.
|
|
190
190
|
|
|
191
|
-
<a id="rules-criteria-virtual-network"></a>• [`virtual_network`](#rules-criteria-virtual-network) - Optional Block<br>
|
|
191
|
+
<a id="rules-criteria-virtual-network"></a>• [`virtual_network`](#rules-criteria-virtual-network) - Optional Block<br>Carries the reference to virtual network<br>See [Virtual Network](#rules-criteria-virtual-network) below.
|
|
192
192
|
|
|
193
193
|
#### Rules Criteria Destination Port
|
|
194
194
|
|
|
195
195
|
A [`destination_port`](#rules-criteria-destination-port) block (within [`rules.criteria`](#rules-criteria)) supports the following:
|
|
196
196
|
|
|
197
|
-
<a id="match-408035"></a>• [`no_port_match`](#match-408035) - Optional Block<br>
|
|
197
|
+
<a id="match-408035"></a>• [`no_port_match`](#match-408035) - Optional Block<br>Can be used for messages where no values are needed
|
|
198
198
|
|
|
199
|
-
<a id="rules-criteria-destination-port-port"></a>• [`port`](#rules-criteria-destination-port-port) - Optional Number<br>
|
|
199
|
+
<a id="rules-criteria-destination-port-port"></a>• [`port`](#rules-criteria-destination-port-port) - Optional Number<br>Exact Port to match
|
|
200
200
|
|
|
201
|
-
<a id="ranges-c8d271"></a>• [`port_ranges`](#ranges-c8d271) - Optional String<br>Port range
|
|
201
|
+
<a id="ranges-c8d271"></a>• [`port_ranges`](#ranges-c8d271) - Optional String<br>Port range to match
|
|
202
202
|
|
|
203
203
|
#### Rules Criteria Segment
|
|
204
204
|
|
|
205
205
|
A [`segment`](#rules-criteria-segment) block (within [`rules.criteria`](#rules-criteria)) supports the following:
|
|
206
206
|
|
|
207
|
-
<a id="rules-criteria-segment-refs"></a>• [`refs`](#rules-criteria-segment-refs) - Optional Block<br>
|
|
207
|
+
<a id="rules-criteria-segment-refs"></a>• [`refs`](#rules-criteria-segment-refs) - Optional Block<br>Reference to Segment Object<br>See [Refs](#rules-criteria-segment-refs) below.
|
|
208
208
|
|
|
209
209
|
#### Rules Criteria Segment Refs
|
|
210
210
|
|
|
211
211
|
A [`refs`](#rules-criteria-segment-refs) block (within [`rules.criteria.segment`](#rules-criteria-segment)) supports the following:
|
|
212
212
|
|
|
213
|
-
<a id="rules-criteria-segment-refs-kind"></a>• [`kind`](#rules-criteria-segment-refs-kind) - Optional String<br>
|
|
213
|
+
<a id="rules-criteria-segment-refs-kind"></a>• [`kind`](#rules-criteria-segment-refs-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')
|
|
214
214
|
|
|
215
|
-
<a id="rules-criteria-segment-refs-name"></a>• [`name`](#rules-criteria-segment-refs-name) - Optional String<br>
|
|
215
|
+
<a id="rules-criteria-segment-refs-name"></a>• [`name`](#rules-criteria-segment-refs-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
|
|
216
216
|
|
|
217
|
-
<a id="rules-criteria-segment-refs-namespace"></a>• [`namespace`](#rules-criteria-segment-refs-namespace) - Optional String<br>
|
|
217
|
+
<a id="rules-criteria-segment-refs-namespace"></a>• [`namespace`](#rules-criteria-segment-refs-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
|
|
218
218
|
|
|
219
|
-
<a id="rules-criteria-segment-refs-tenant"></a>• [`tenant`](#rules-criteria-segment-refs-tenant) - Optional String<br>
|
|
219
|
+
<a id="rules-criteria-segment-refs-tenant"></a>• [`tenant`](#rules-criteria-segment-refs-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
|
|
220
220
|
|
|
221
|
-
<a id="rules-criteria-segment-refs-uid"></a>• [`uid`](#rules-criteria-segment-refs-uid) - Optional String<br>
|
|
221
|
+
<a id="rules-criteria-segment-refs-uid"></a>• [`uid`](#rules-criteria-segment-refs-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
|
|
222
222
|
|
|
223
223
|
#### Rules Criteria Source Port
|
|
224
224
|
|
|
225
225
|
A [`source_port`](#rules-criteria-source-port) block (within [`rules.criteria`](#rules-criteria)) supports the following:
|
|
226
226
|
|
|
227
|
-
<a id="match-b33190"></a>• [`no_port_match`](#match-b33190) - Optional Block<br>
|
|
227
|
+
<a id="match-b33190"></a>• [`no_port_match`](#match-b33190) - Optional Block<br>Can be used for messages where no values are needed
|
|
228
228
|
|
|
229
|
-
<a id="rules-criteria-source-port-port"></a>• [`port`](#rules-criteria-source-port-port) - Optional Number<br>
|
|
229
|
+
<a id="rules-criteria-source-port-port"></a>• [`port`](#rules-criteria-source-port-port) - Optional Number<br>Exact Port to match
|
|
230
230
|
|
|
231
|
-
<a id="rules-criteria-source-port-port-ranges"></a>• [`port_ranges`](#rules-criteria-source-port-port-ranges) - Optional String<br>Port range
|
|
231
|
+
<a id="rules-criteria-source-port-port-ranges"></a>• [`port_ranges`](#rules-criteria-source-port-port-ranges) - Optional String<br>Port range to match
|
|
232
232
|
|
|
233
233
|
#### Rules Criteria TCP
|
|
234
234
|
|
|
235
235
|
A [`tcp`](#rules-criteria-tcp) block (within [`rules.criteria`](#rules-criteria)) supports the following:
|
|
236
236
|
|
|
237
|
-
<a id="rules-criteria-tcp-destination-port"></a>• [`destination_port`](#rules-criteria-tcp-destination-port) - Optional Block<br>Port
|
|
237
|
+
<a id="rules-criteria-tcp-destination-port"></a>• [`destination_port`](#rules-criteria-tcp-destination-port) - Optional Block<br>Port match of the request can be a range or a specific port<br>See [Destination Port](#rules-criteria-tcp-destination-port) below.
|
|
238
238
|
|
|
239
|
-
<a id="rules-criteria-tcp-source-port"></a>• [`source_port`](#rules-criteria-tcp-source-port) - Optional Block<br>Port
|
|
239
|
+
<a id="rules-criteria-tcp-source-port"></a>• [`source_port`](#rules-criteria-tcp-source-port) - Optional Block<br>Port match of the request can be a range or a specific port<br>See [Source Port](#rules-criteria-tcp-source-port) below.
|
|
240
240
|
|
|
241
241
|
#### Rules Criteria TCP Destination Port
|
|
242
242
|
|
|
243
243
|
A [`destination_port`](#rules-criteria-tcp-destination-port) block (within [`rules.criteria.tcp`](#rules-criteria-tcp)) supports the following:
|
|
244
244
|
|
|
245
|
-
<a id="match-d7a933"></a>• [`no_port_match`](#match-d7a933) - Optional Block<br>
|
|
245
|
+
<a id="match-d7a933"></a>• [`no_port_match`](#match-d7a933) - Optional Block<br>Can be used for messages where no values are needed
|
|
246
246
|
|
|
247
|
-
<a id="port-8bd6fd"></a>• [`port`](#port-8bd6fd) - Optional Number<br>
|
|
247
|
+
<a id="port-8bd6fd"></a>• [`port`](#port-8bd6fd) - Optional Number<br>Exact Port to match
|
|
248
248
|
|
|
249
|
-
<a id="ranges-d800d8"></a>• [`port_ranges`](#ranges-d800d8) - Optional String<br>Port range
|
|
249
|
+
<a id="ranges-d800d8"></a>• [`port_ranges`](#ranges-d800d8) - Optional String<br>Port range to match
|
|
250
250
|
|
|
251
251
|
#### Rules Criteria TCP Source Port
|
|
252
252
|
|
|
253
253
|
A [`source_port`](#rules-criteria-tcp-source-port) block (within [`rules.criteria.tcp`](#rules-criteria-tcp)) supports the following:
|
|
254
254
|
|
|
255
|
-
<a id="match-dbf0f6"></a>• [`no_port_match`](#match-dbf0f6) - Optional Block<br>
|
|
255
|
+
<a id="match-dbf0f6"></a>• [`no_port_match`](#match-dbf0f6) - Optional Block<br>Can be used for messages where no values are needed
|
|
256
256
|
|
|
257
|
-
<a id="rules-criteria-tcp-source-port-port"></a>• [`port`](#rules-criteria-tcp-source-port-port) - Optional Number<br>
|
|
257
|
+
<a id="rules-criteria-tcp-source-port-port"></a>• [`port`](#rules-criteria-tcp-source-port-port) - Optional Number<br>Exact Port to match
|
|
258
258
|
|
|
259
|
-
<a id="ranges-8fd5fe"></a>• [`port_ranges`](#ranges-8fd5fe) - Optional String<br>Port range
|
|
259
|
+
<a id="ranges-8fd5fe"></a>• [`port_ranges`](#ranges-8fd5fe) - Optional String<br>Port range to match
|
|
260
260
|
|
|
261
261
|
#### Rules Criteria UDP
|
|
262
262
|
|
|
263
263
|
An [`udp`](#rules-criteria-udp) block (within [`rules.criteria`](#rules-criteria)) supports the following:
|
|
264
264
|
|
|
265
|
-
<a id="rules-criteria-udp-destination-port"></a>• [`destination_port`](#rules-criteria-udp-destination-port) - Optional Block<br>Port
|
|
265
|
+
<a id="rules-criteria-udp-destination-port"></a>• [`destination_port`](#rules-criteria-udp-destination-port) - Optional Block<br>Port match of the request can be a range or a specific port<br>See [Destination Port](#rules-criteria-udp-destination-port) below.
|
|
266
266
|
|
|
267
|
-
<a id="rules-criteria-udp-source-port"></a>• [`source_port`](#rules-criteria-udp-source-port) - Optional Block<br>Port
|
|
267
|
+
<a id="rules-criteria-udp-source-port"></a>• [`source_port`](#rules-criteria-udp-source-port) - Optional Block<br>Port match of the request can be a range or a specific port<br>See [Source Port](#rules-criteria-udp-source-port) below.
|
|
268
268
|
|
|
269
269
|
#### Rules Criteria UDP Destination Port
|
|
270
270
|
|
|
271
271
|
A [`destination_port`](#rules-criteria-udp-destination-port) block (within [`rules.criteria.udp`](#rules-criteria-udp)) supports the following:
|
|
272
272
|
|
|
273
|
-
<a id="match-214578"></a>• [`no_port_match`](#match-214578) - Optional Block<br>
|
|
273
|
+
<a id="match-214578"></a>• [`no_port_match`](#match-214578) - Optional Block<br>Can be used for messages where no values are needed
|
|
274
274
|
|
|
275
|
-
<a id="port-955148"></a>• [`port`](#port-955148) - Optional Number<br>
|
|
275
|
+
<a id="port-955148"></a>• [`port`](#port-955148) - Optional Number<br>Exact Port to match
|
|
276
276
|
|
|
277
|
-
<a id="ranges-6407dd"></a>• [`port_ranges`](#ranges-6407dd) - Optional String<br>Port range
|
|
277
|
+
<a id="ranges-6407dd"></a>• [`port_ranges`](#ranges-6407dd) - Optional String<br>Port range to match
|
|
278
278
|
|
|
279
279
|
#### Rules Criteria UDP Source Port
|
|
280
280
|
|
|
281
281
|
A [`source_port`](#rules-criteria-udp-source-port) block (within [`rules.criteria.udp`](#rules-criteria-udp)) supports the following:
|
|
282
282
|
|
|
283
|
-
<a id="match-2dbf46"></a>• [`no_port_match`](#match-2dbf46) - Optional Block<br>
|
|
283
|
+
<a id="match-2dbf46"></a>• [`no_port_match`](#match-2dbf46) - Optional Block<br>Can be used for messages where no values are needed
|
|
284
284
|
|
|
285
|
-
<a id="rules-criteria-udp-source-port-port"></a>• [`port`](#rules-criteria-udp-source-port-port) - Optional Number<br>
|
|
285
|
+
<a id="rules-criteria-udp-source-port-port"></a>• [`port`](#rules-criteria-udp-source-port-port) - Optional Number<br>Exact Port to match
|
|
286
286
|
|
|
287
|
-
<a id="ranges-a44153"></a>• [`port_ranges`](#ranges-a44153) - Optional String<br>Port range
|
|
287
|
+
<a id="ranges-a44153"></a>• [`port_ranges`](#ranges-a44153) - Optional String<br>Port range to match
|
|
288
288
|
|
|
289
289
|
#### Rules Criteria Virtual Network
|
|
290
290
|
|
|
@@ -296,55 +296,55 @@ A [`virtual_network`](#rules-criteria-virtual-network) block (within [`rules.cri
|
|
|
296
296
|
|
|
297
297
|
A [`refs`](#rules-criteria-virtual-network-refs) block (within [`rules.criteria.virtual_network`](#rules-criteria-virtual-network)) supports the following:
|
|
298
298
|
|
|
299
|
-
<a id="kind-8d8876"></a>• [`kind`](#kind-8d8876) - Optional String<br>
|
|
299
|
+
<a id="kind-8d8876"></a>• [`kind`](#kind-8d8876) - 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')
|
|
300
300
|
|
|
301
|
-
<a id="name-369d2b"></a>• [`name`](#name-369d2b) - Optional String<br>
|
|
301
|
+
<a id="name-369d2b"></a>• [`name`](#name-369d2b) - 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
|
|
302
302
|
|
|
303
|
-
<a id="namespace-a79f74"></a>• [`namespace`](#namespace-a79f74) - Optional String<br>
|
|
303
|
+
<a id="namespace-a79f74"></a>• [`namespace`](#namespace-a79f74) - 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
|
|
304
304
|
|
|
305
|
-
<a id="tenant-79ff48"></a>• [`tenant`](#tenant-79ff48) - Optional String<br>
|
|
305
|
+
<a id="tenant-79ff48"></a>• [`tenant`](#tenant-79ff48) - 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
|
|
306
306
|
|
|
307
|
-
<a id="rules-criteria-virtual-network-refs-uid"></a>• [`uid`](#rules-criteria-virtual-network-refs-uid) - Optional String<br>
|
|
307
|
+
<a id="rules-criteria-virtual-network-refs-uid"></a>• [`uid`](#rules-criteria-virtual-network-refs-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
|
|
308
308
|
|
|
309
309
|
#### Rules Network Interface
|
|
310
310
|
|
|
311
311
|
A [`network_interface`](#rules-network-interface) block (within [`rules`](#rules)) supports the following:
|
|
312
312
|
|
|
313
|
-
<a id="rules-network-interface-refs"></a>• [`refs`](#rules-network-interface-refs) - Optional Block<br>
|
|
313
|
+
<a id="rules-network-interface-refs"></a>• [`refs`](#rules-network-interface-refs) - Optional Block<br>Reference to Network Interface Object<br>See [Refs](#rules-network-interface-refs) below.
|
|
314
314
|
|
|
315
315
|
#### Rules Network Interface Refs
|
|
316
316
|
|
|
317
317
|
A [`refs`](#rules-network-interface-refs) block (within [`rules.network_interface`](#rules-network-interface)) supports the following:
|
|
318
318
|
|
|
319
|
-
<a id="rules-network-interface-refs-kind"></a>• [`kind`](#rules-network-interface-refs-kind) - Optional String<br>
|
|
319
|
+
<a id="rules-network-interface-refs-kind"></a>• [`kind`](#rules-network-interface-refs-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')
|
|
320
320
|
|
|
321
|
-
<a id="rules-network-interface-refs-name"></a>• [`name`](#rules-network-interface-refs-name) - Optional String<br>
|
|
321
|
+
<a id="rules-network-interface-refs-name"></a>• [`name`](#rules-network-interface-refs-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
|
|
322
322
|
|
|
323
|
-
<a id="rules-network-interface-refs-namespace"></a>• [`namespace`](#rules-network-interface-refs-namespace) - Optional String<br>
|
|
323
|
+
<a id="rules-network-interface-refs-namespace"></a>• [`namespace`](#rules-network-interface-refs-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
|
|
324
324
|
|
|
325
|
-
<a id="rules-network-interface-refs-tenant"></a>• [`tenant`](#rules-network-interface-refs-tenant) - Optional String<br>
|
|
325
|
+
<a id="rules-network-interface-refs-tenant"></a>• [`tenant`](#rules-network-interface-refs-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
|
|
326
326
|
|
|
327
|
-
<a id="rules-network-interface-refs-uid"></a>• [`uid`](#rules-network-interface-refs-uid) - Optional String<br>
|
|
327
|
+
<a id="rules-network-interface-refs-uid"></a>• [`uid`](#rules-network-interface-refs-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
|
|
328
328
|
|
|
329
329
|
#### Rules Segment
|
|
330
330
|
|
|
331
331
|
A [`segment`](#rules-segment) block (within [`rules`](#rules)) supports the following:
|
|
332
332
|
|
|
333
|
-
<a id="rules-segment-refs"></a>• [`refs`](#rules-segment-refs) - Optional Block<br>
|
|
333
|
+
<a id="rules-segment-refs"></a>• [`refs`](#rules-segment-refs) - Optional Block<br>Reference to Segment Object<br>See [Refs](#rules-segment-refs) below.
|
|
334
334
|
|
|
335
335
|
#### Rules Segment Refs
|
|
336
336
|
|
|
337
337
|
A [`refs`](#rules-segment-refs) block (within [`rules.segment`](#rules-segment)) supports the following:
|
|
338
338
|
|
|
339
|
-
<a id="rules-segment-refs-kind"></a>• [`kind`](#rules-segment-refs-kind) - Optional String<br>
|
|
339
|
+
<a id="rules-segment-refs-kind"></a>• [`kind`](#rules-segment-refs-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')
|
|
340
340
|
|
|
341
|
-
<a id="rules-segment-refs-name"></a>• [`name`](#rules-segment-refs-name) - Optional String<br>
|
|
341
|
+
<a id="rules-segment-refs-name"></a>• [`name`](#rules-segment-refs-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
|
|
342
342
|
|
|
343
|
-
<a id="rules-segment-refs-namespace"></a>• [`namespace`](#rules-segment-refs-namespace) - Optional String<br>
|
|
343
|
+
<a id="rules-segment-refs-namespace"></a>• [`namespace`](#rules-segment-refs-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
|
|
344
344
|
|
|
345
|
-
<a id="rules-segment-refs-tenant"></a>• [`tenant`](#rules-segment-refs-tenant) - Optional String<br>
|
|
345
|
+
<a id="rules-segment-refs-tenant"></a>• [`tenant`](#rules-segment-refs-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
|
|
346
346
|
|
|
347
|
-
<a id="rules-segment-refs-uid"></a>• [`uid`](#rules-segment-refs-uid) - Optional String<br>
|
|
347
|
+
<a id="rules-segment-refs-uid"></a>• [`uid`](#rules-segment-refs-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
|
|
348
348
|
|
|
349
349
|
#### Rules Virtual Network
|
|
350
350
|
|
|
@@ -356,15 +356,15 @@ A [`virtual_network`](#rules-virtual-network) block (within [`rules`](#rules)) s
|
|
|
356
356
|
|
|
357
357
|
A [`refs`](#rules-virtual-network-refs) block (within [`rules.virtual_network`](#rules-virtual-network)) supports the following:
|
|
358
358
|
|
|
359
|
-
<a id="rules-virtual-network-refs-kind"></a>• [`kind`](#rules-virtual-network-refs-kind) - Optional String<br>
|
|
359
|
+
<a id="rules-virtual-network-refs-kind"></a>• [`kind`](#rules-virtual-network-refs-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')
|
|
360
360
|
|
|
361
|
-
<a id="rules-virtual-network-refs-name"></a>• [`name`](#rules-virtual-network-refs-name) - Optional String<br>
|
|
361
|
+
<a id="rules-virtual-network-refs-name"></a>• [`name`](#rules-virtual-network-refs-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
|
|
362
362
|
|
|
363
|
-
<a id="rules-virtual-network-refs-namespace"></a>• [`namespace`](#rules-virtual-network-refs-namespace) - Optional String<br>
|
|
363
|
+
<a id="rules-virtual-network-refs-namespace"></a>• [`namespace`](#rules-virtual-network-refs-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
|
|
364
364
|
|
|
365
|
-
<a id="rules-virtual-network-refs-tenant"></a>• [`tenant`](#rules-virtual-network-refs-tenant) - Optional String<br>
|
|
365
|
+
<a id="rules-virtual-network-refs-tenant"></a>• [`tenant`](#rules-virtual-network-refs-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
|
|
366
366
|
|
|
367
|
-
<a id="rules-virtual-network-refs-uid"></a>• [`uid`](#rules-virtual-network-refs-uid) - Optional String<br>
|
|
367
|
+
<a id="rules-virtual-network-refs-uid"></a>• [`uid`](#rules-virtual-network-refs-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
|
|
368
368
|
|
|
369
369
|
#### Site
|
|
370
370
|
|
|
@@ -376,15 +376,15 @@ A [`site`](#site) block supports the following:
|
|
|
376
376
|
|
|
377
377
|
A [`refs`](#site-refs) block (within [`site`](#site)) supports the following:
|
|
378
378
|
|
|
379
|
-
<a id="site-refs-kind"></a>• [`kind`](#site-refs-kind) - Optional String<br>
|
|
379
|
+
<a id="site-refs-kind"></a>• [`kind`](#site-refs-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')
|
|
380
380
|
|
|
381
|
-
<a id="site-refs-name"></a>• [`name`](#site-refs-name) - Optional String<br>
|
|
381
|
+
<a id="site-refs-name"></a>• [`name`](#site-refs-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
|
|
382
382
|
|
|
383
|
-
<a id="site-refs-namespace"></a>• [`namespace`](#site-refs-namespace) - Optional String<br>
|
|
383
|
+
<a id="site-refs-namespace"></a>• [`namespace`](#site-refs-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
|
|
384
384
|
|
|
385
|
-
<a id="site-refs-tenant"></a>• [`tenant`](#site-refs-tenant) - Optional String<br>
|
|
385
|
+
<a id="site-refs-tenant"></a>• [`tenant`](#site-refs-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
|
|
386
386
|
|
|
387
|
-
<a id="site-refs-uid"></a>• [`uid`](#site-refs-uid) - Optional String<br>
|
|
387
|
+
<a id="site-refs-uid"></a>• [`uid`](#site-refs-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
|
|
388
388
|
|
|
389
389
|
#### Timeouts
|
|
390
390
|
|