@robinmordasiewicz/f5xc-terraform-mcp 3.10.2 → 3.10.4
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/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/log_receiver.md +2 -2
- package/dist/docs/data-sources/network_policy.md +2 -2
- package/dist/docs/data-sources/site.md +2 -2
- package/dist/docs/resources/advertise_policy.md +10 -10
- package/dist/docs/resources/alert_policy.md +9 -9
- package/dist/docs/resources/alert_receiver.md +4 -4
- package/dist/docs/resources/api_definition.md +2 -2
- package/dist/docs/resources/api_testing.md +6 -6
- package/dist/docs/resources/apm.md +8 -8
- package/dist/docs/resources/app_firewall.md +19 -19
- package/dist/docs/resources/app_setting.md +5 -5
- package/dist/docs/resources/app_type.md +3 -3
- package/dist/docs/resources/aws_tgw_site.md +50 -50
- package/dist/docs/resources/aws_vpc_site.md +66 -66
- package/dist/docs/resources/azure_vnet_site.md +93 -93
- package/dist/docs/resources/bgp.md +205 -37
- package/dist/docs/resources/bgp_routing_policy.md +7 -7
- package/dist/docs/resources/cdn_cache_rule.md +2 -2
- package/dist/docs/resources/cdn_loadbalancer.md +122 -122
- package/dist/docs/resources/cloud_connect.md +2 -2
- package/dist/docs/resources/cloud_credentials.md +2 -2
- package/dist/docs/resources/cloud_link.md +3 -3
- package/dist/docs/resources/cluster.md +18 -18
- package/dist/docs/resources/dc_cluster_group.md +4 -4
- package/dist/docs/resources/discovery.md +259 -8
- package/dist/docs/resources/dns_domain.md +2 -2
- package/dist/docs/resources/endpoint.md +5 -5
- package/dist/docs/resources/enhanced_firewall_policy.md +15 -15
- package/dist/docs/resources/external_connector.md +7 -7
- package/dist/docs/resources/fast_acl.md +166 -60
- package/dist/docs/resources/fast_acl_rule.md +2 -2
- package/dist/docs/resources/fleet.md +25 -25
- package/dist/docs/resources/forward_proxy_policy.md +15 -15
- package/dist/docs/resources/forwarding_class.md +5 -5
- package/dist/docs/resources/gcp_vpc_site.md +37 -37
- package/dist/docs/resources/global_log_receiver.md +104 -104
- package/dist/docs/resources/healthcheck.md +2 -2
- package/dist/docs/resources/http_loadbalancer.md +287 -287
- package/dist/docs/resources/log_receiver.md +44 -825
- package/dist/docs/resources/malicious_user_mitigation.md +6 -6
- package/dist/docs/resources/nat_policy.md +10 -10
- package/dist/docs/resources/network_connector.md +9 -9
- package/dist/docs/resources/network_firewall.md +3 -3
- package/dist/docs/resources/network_interface.md +28 -28
- package/dist/docs/resources/network_policy.md +217 -38
- package/dist/docs/resources/network_policy_view.md +16 -16
- package/dist/docs/resources/nfv_service.md +26 -26
- package/dist/docs/resources/origin_pool.md +48 -48
- package/dist/docs/resources/policy_based_routing.md +8 -8
- package/dist/docs/resources/protocol_inspection.md +4 -4
- package/dist/docs/resources/proxy.md +23 -23
- package/dist/docs/resources/rate_limiter.md +1 -1
- package/dist/docs/resources/rate_limiter_policy.md +8 -8
- package/dist/docs/resources/route.md +36 -36
- package/dist/docs/resources/secret_management_access.md +8 -8
- package/dist/docs/resources/securemesh_site.md +258 -1619
- package/dist/docs/resources/segment.md +4 -4
- package/dist/docs/resources/service_policy.md +44 -44
- package/dist/docs/resources/service_policy_rule.md +37 -37
- package/dist/docs/resources/site.md +244 -322
- package/dist/docs/resources/site_mesh_group.md +8 -8
- package/dist/docs/resources/subnet.md +5 -5
- package/dist/docs/resources/tcp_loadbalancer.md +37 -37
- package/dist/docs/resources/tunnel.md +4 -4
- package/dist/docs/resources/udp_loadbalancer.md +9 -9
- package/dist/docs/resources/user_identification.md +10 -10
- package/dist/docs/resources/virtual_host.md +42 -42
- package/dist/docs/resources/virtual_network.md +4 -4
- package/dist/docs/resources/voltstack_site.md +59 -59
- package/dist/docs/resources/waf_exclusion_policy.md +5 -5
- package/dist/docs/resources/workload.md +24 -24
- package/dist/metadata/resource-metadata.json +394 -948
- package/dist/metadata/validation-patterns.json +1 -1
- package/package.json +1 -1
|
@@ -2,12 +2,12 @@
|
|
|
2
2
|
page_title: "f5xc_network_policy Resource - terraform-provider-f5xc"
|
|
3
3
|
subcategory: "Security"
|
|
4
4
|
description: |-
|
|
5
|
-
Manages network policy
|
|
5
|
+
Manages new network policy with configured parameters in specified namespace. in F5 Distributed Cloud.
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# f5xc_network_policy (Resource)
|
|
9
9
|
|
|
10
|
-
Manages network policy
|
|
10
|
+
Manages new network policy with configured parameters in specified namespace. in F5 Distributed Cloud.
|
|
11
11
|
|
|
12
12
|
~> **Note** For more information about this resource, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
|
|
13
13
|
|
|
@@ -15,7 +15,7 @@ Manages network policy rule with configured parameters in specified namespace. i
|
|
|
15
15
|
|
|
16
16
|
```terraform
|
|
17
17
|
# Network Policy Resource Example
|
|
18
|
-
# Manages network policy
|
|
18
|
+
# Manages new network policy with configured parameters in specified namespace. in F5 Distributed Cloud.
|
|
19
19
|
|
|
20
20
|
# Basic Network Policy configuration
|
|
21
21
|
resource "f5xc_network_policy" "example" {
|
|
@@ -77,20 +77,9 @@ resource "f5xc_network_policy" "example" {
|
|
|
77
77
|
|
|
78
78
|
### Spec Argument Reference
|
|
79
79
|
|
|
80
|
-
<a id="
|
|
80
|
+
<a id="endpoint"></a>• [`endpoint`](#endpoint) - Optional Block<br>Shape of the endpoint choices for a view<br>See [Endpoint](#endpoint) below for details.
|
|
81
81
|
|
|
82
|
-
<a id="
|
|
83
|
-
|
|
84
|
-
-> **One of the following:**
|
|
85
|
-
• <a id="ip-prefix-set"></a>[`ip_prefix_set`](#ip-prefix-set) - Optional Block<br>List of references to ip_prefix_set objects<br>See [IP Prefix Set](#ip-prefix-set) below for details.
|
|
86
|
-
<br><br>• <a id="prefix"></a>[`prefix`](#prefix) - Optional Block<br>List of IP Address prefixes. Prefix must contain both prefix and prefix-length The list can contain mix of both IPv4 and IPv6 prefixes<br>See [Prefix](#prefix) below for details.
|
|
87
|
-
<br><br>• <a id="prefix-selector"></a>[`prefix_selector`](#prefix-selector) - Optional Block<br>Type can be used to establish a 'selector reference' from one object(called selector) to a set of other objects(called selectees) based on the value of expresssions. A label selector is a label query over a set of resources. An empty label selector matches all objects<br>See [Prefix Selector](#prefix-selector) below for details.
|
|
88
|
-
|
|
89
|
-
<a id="label-matcher"></a>• [`label_matcher`](#label-matcher) - Optional Block<br>Label matcher specifies a list of label keys whose values need to match for source/client and destination/server. Note that the actual label values are not specified and do not matter. This allows an ability to scope grouping by the label key name<br>See [Label Matcher](#label-matcher) below for details.
|
|
90
|
-
|
|
91
|
-
<a id="ports"></a>• [`ports`](#ports) - Optional List<br>List of port ranges. Each range is a single port or a pair of start and end ports e.g. 8080-8192
|
|
92
|
-
|
|
93
|
-
<a id="protocol"></a>• [`protocol`](#protocol) - Optional String<br>Protocol in IP packet to be used as match criteria Values are TCP, UDP, and ICMP
|
|
82
|
+
<a id="rules"></a>• [`rules`](#rules) - Optional Block<br>Rule Choice. Shape of Rule Choice<br>See [Rules](#rules) below for details.
|
|
94
83
|
|
|
95
84
|
<a id="timeouts"></a>• [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
|
|
96
85
|
|
|
@@ -102,49 +91,239 @@ In addition to all arguments above, the following attributes are exported:
|
|
|
102
91
|
|
|
103
92
|
---
|
|
104
93
|
|
|
105
|
-
####
|
|
94
|
+
#### Endpoint
|
|
95
|
+
|
|
96
|
+
An [`endpoint`](#endpoint) block supports the following:
|
|
97
|
+
|
|
98
|
+
<a id="endpoint-any"></a>• [`any`](#endpoint-any) - Optional Block<br>Enable this option
|
|
99
|
+
|
|
100
|
+
<a id="endpoint-inside-endpoints"></a>• [`inside_endpoints`](#endpoint-inside-endpoints) - Optional Block<br>Enable this option
|
|
101
|
+
|
|
102
|
+
<a id="endpoint-label-selector"></a>• [`label_selector`](#endpoint-label-selector) - Optional Block<br>Type can be used to establish a 'selector reference' from one object(called selector) to a set of other objects(called selectees) based on the value of expresssions. A label selector is a label query over a set of resources. An empty label selector matches all objects<br>See [Label Selector](#endpoint-label-selector) below.
|
|
103
|
+
|
|
104
|
+
<a id="endpoint-outside-endpoints"></a>• [`outside_endpoints`](#endpoint-outside-endpoints) - Optional Block<br>Enable this option
|
|
105
|
+
|
|
106
|
+
<a id="endpoint-prefix-list"></a>• [`prefix_list`](#endpoint-prefix-list) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Prefix List](#endpoint-prefix-list) below.
|
|
107
|
+
|
|
108
|
+
#### Endpoint Label Selector
|
|
109
|
+
|
|
110
|
+
A [`label_selector`](#endpoint-label-selector) block (within [`endpoint`](#endpoint)) supports the following:
|
|
111
|
+
|
|
112
|
+
<a id="endpoint-label-selector-expressions"></a>• [`expressions`](#endpoint-label-selector-expressions) - Optional List<br>Expressions contains the Kubernetes style label expression for selections
|
|
113
|
+
|
|
114
|
+
#### Endpoint Prefix List
|
|
115
|
+
|
|
116
|
+
A [`prefix_list`](#endpoint-prefix-list) block (within [`endpoint`](#endpoint)) supports the following:
|
|
117
|
+
|
|
118
|
+
<a id="endpoint-prefix-list-prefixes"></a>• [`prefixes`](#endpoint-prefix-list-prefixes) - Optional List<br>List of IPv4 prefixes that represent an endpoint
|
|
119
|
+
|
|
120
|
+
#### Rules
|
|
121
|
+
|
|
122
|
+
A [`rules`](#rules) block supports the following:
|
|
123
|
+
|
|
124
|
+
<a id="rules-egress-rules"></a>• [`egress_rules`](#rules-egress-rules) - Optional Block<br>Ordered list of rules applied to connections from policy endpoints<br>See [Egress Rules](#rules-egress-rules) below.
|
|
125
|
+
|
|
126
|
+
<a id="rules-ingress-rules"></a>• [`ingress_rules`](#rules-ingress-rules) - Optional Block<br>Ordered list of rules applied to connections to policy endpoints<br>See [Ingress Rules](#rules-ingress-rules) below.
|
|
127
|
+
|
|
128
|
+
#### Rules Egress Rules
|
|
129
|
+
|
|
130
|
+
An [`egress_rules`](#rules-egress-rules) block (within [`rules`](#rules)) supports the following:
|
|
131
|
+
|
|
132
|
+
<a id="rules-egress-rules-action"></a>• [`action`](#rules-egress-rules-action) - Optional String Defaults to `DENY`<br>Possible values are `DENY`, `ALLOW`<br>[Enum: DENY|ALLOW] Network policy rule action configures the action to be taken on rule match Apply deny action on rule match Apply allow action on rule match
|
|
133
|
+
|
|
134
|
+
<a id="rules-egress-rules-adv-action"></a>• [`adv_action`](#rules-egress-rules-adv-action) - Optional Block<br>Network Policy Rule Advanced Action provides additional OPTIONS along with RuleAction and PBRRuleAction<br>See [Adv Action](#rules-egress-rules-adv-action) below.
|
|
135
|
+
|
|
136
|
+
<a id="rules-egress-rules-all-tcp-traffic"></a>• [`all_tcp_traffic`](#rules-egress-rules-all-tcp-traffic) - Optional Block<br>Enable this option
|
|
137
|
+
|
|
138
|
+
<a id="rules-egress-rules-all-traffic"></a>• [`all_traffic`](#rules-egress-rules-all-traffic) - Optional Block<br>Enable this option
|
|
139
|
+
|
|
140
|
+
<a id="rules-egress-rules-all-udp-traffic"></a>• [`all_udp_traffic`](#rules-egress-rules-all-udp-traffic) - Optional Block<br>Enable this option
|
|
141
|
+
|
|
142
|
+
<a id="rules-egress-rules-any"></a>• [`any`](#rules-egress-rules-any) - Optional Block<br>Enable this option
|
|
143
|
+
|
|
144
|
+
<a id="rules-egress-rules-applications"></a>• [`applications`](#rules-egress-rules-applications) - Optional Block<br>Applications. Application protocols like HTTP, SNMP<br>See [Applications](#rules-egress-rules-applications) below.
|
|
145
|
+
|
|
146
|
+
<a id="rules-egress-rules-inside-endpoints"></a>• [`inside_endpoints`](#rules-egress-rules-inside-endpoints) - Optional Block<br>Enable this option
|
|
147
|
+
|
|
148
|
+
<a id="rules-egress-rules-ip-prefix-set"></a>• [`ip_prefix_set`](#rules-egress-rules-ip-prefix-set) - Optional Block<br>List of references to ip_prefix_set objects<br>See [IP Prefix Set](#rules-egress-rules-ip-prefix-set) below.
|
|
149
|
+
|
|
150
|
+
<a id="rules-egress-rules-label-matcher"></a>• [`label_matcher`](#rules-egress-rules-label-matcher) - Optional Block<br>Label matcher specifies a list of label keys whose values need to match for source/client and destination/server. Note that the actual label values are not specified and do not matter. This allows an ability to scope grouping by the label key name<br>See [Label Matcher](#rules-egress-rules-label-matcher) below.
|
|
151
|
+
|
|
152
|
+
<a id="rules-egress-rules-label-selector"></a>• [`label_selector`](#rules-egress-rules-label-selector) - Optional Block<br>Type can be used to establish a 'selector reference' from one object(called selector) to a set of other objects(called selectees) based on the value of expresssions. A label selector is a label query over a set of resources. An empty label selector matches all objects<br>See [Label Selector](#rules-egress-rules-label-selector) below.
|
|
153
|
+
|
|
154
|
+
<a id="rules-egress-rules-metadata"></a>• [`metadata`](#rules-egress-rules-metadata) - Optional Block<br>MessageMetaType is metadata (common attributes) of a message that only certain messages have. This information is propagated to the metadata of a child object that gets created from the containing message during view processing. The information in this type can be specified by user during create<br>See [Metadata](#rules-egress-rules-metadata) below.
|
|
155
|
+
|
|
156
|
+
<a id="rules-egress-rules-outside-endpoints"></a>• [`outside_endpoints`](#rules-egress-rules-outside-endpoints) - Optional Block<br>Enable this option
|
|
157
|
+
|
|
158
|
+
<a id="rules-egress-rules-prefix-list"></a>• [`prefix_list`](#rules-egress-rules-prefix-list) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Prefix List](#rules-egress-rules-prefix-list) below.
|
|
159
|
+
|
|
160
|
+
<a id="rules-egress-rules-protocol-port-range"></a>• [`protocol_port_range`](#rules-egress-rules-protocol-port-range) - Optional Block<br>Protocol and Port. Protocol and Port ranges<br>See [Protocol Port Range](#rules-egress-rules-protocol-port-range) below.
|
|
161
|
+
|
|
162
|
+
#### Rules Egress Rules Adv Action
|
|
163
|
+
|
|
164
|
+
An [`adv_action`](#rules-egress-rules-adv-action) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
165
|
+
|
|
166
|
+
<a id="rules-egress-rules-adv-action-action"></a>• [`action`](#rules-egress-rules-adv-action-action) - Optional String Defaults to `NOLOG`<br>Possible values are `NOLOG`, `LOG`<br>[Enum: NOLOG|LOG] Choice to choose logging or no logging This works together with option selected via NetworkPolicyRuleAction or any other action specified x-
|
|
167
|
+
|
|
168
|
+
#### Rules Egress Rules Applications
|
|
169
|
+
|
|
170
|
+
An [`applications`](#rules-egress-rules-applications) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
171
|
+
|
|
172
|
+
<a id="applications-f7c65d"></a>• [`applications`](#applications-f7c65d) - Optional List Defaults to `APPLICATION_HTTP`<br>Possible values are `APPLICATION_HTTP`, `APPLICATION_HTTPS`, `APPLICATION_SNMP`, `APPLICATION_DNS`<br>[Enum: APPLICATION_HTTP|APPLICATION_HTTPS|APPLICATION_SNMP|APPLICATION_DNS] Application Protocols. Application protocols like HTTP, SNMP
|
|
173
|
+
|
|
174
|
+
#### Rules Egress Rules IP Prefix Set
|
|
175
|
+
|
|
176
|
+
An [`ip_prefix_set`](#rules-egress-rules-ip-prefix-set) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
177
|
+
|
|
178
|
+
<a id="rules-egress-rules-ip-prefix-set-ref"></a>• [`ref`](#rules-egress-rules-ip-prefix-set-ref) - Optional Block<br>List of references to ip_prefix_set objects<br>See [Ref](#rules-egress-rules-ip-prefix-set-ref) below.
|
|
179
|
+
|
|
180
|
+
#### Rules Egress Rules IP Prefix Set Ref
|
|
181
|
+
|
|
182
|
+
A [`ref`](#rules-egress-rules-ip-prefix-set-ref) block (within [`rules.egress_rules.ip_prefix_set`](#rules-egress-rules-ip-prefix-set)) supports the following:
|
|
183
|
+
|
|
184
|
+
<a id="kind-6153e0"></a>• [`kind`](#kind-6153e0) - 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')
|
|
185
|
+
|
|
186
|
+
<a id="name-3c4742"></a>• [`name`](#name-3c4742) - 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
|
|
187
|
+
|
|
188
|
+
<a id="namespace-f39f97"></a>• [`namespace`](#namespace-f39f97) - 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
|
|
189
|
+
|
|
190
|
+
<a id="tenant-5557c0"></a>• [`tenant`](#tenant-5557c0) - 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
|
|
191
|
+
|
|
192
|
+
<a id="uid-b4cc26"></a>• [`uid`](#uid-b4cc26) - 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
|
|
193
|
+
|
|
194
|
+
#### Rules Egress Rules Label Matcher
|
|
195
|
+
|
|
196
|
+
A [`label_matcher`](#rules-egress-rules-label-matcher) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
197
|
+
|
|
198
|
+
<a id="rules-egress-rules-label-matcher-keys"></a>• [`keys`](#rules-egress-rules-label-matcher-keys) - Optional List<br>The list of label key names that have to match
|
|
199
|
+
|
|
200
|
+
#### Rules Egress Rules Label Selector
|
|
201
|
+
|
|
202
|
+
A [`label_selector`](#rules-egress-rules-label-selector) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
203
|
+
|
|
204
|
+
<a id="expressions-d57cba"></a>• [`expressions`](#expressions-d57cba) - Optional List<br>Expressions contains the Kubernetes style label expression for selections
|
|
205
|
+
|
|
206
|
+
#### Rules Egress Rules Metadata
|
|
207
|
+
|
|
208
|
+
A [`metadata`](#rules-egress-rules-metadata) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
209
|
+
|
|
210
|
+
<a id="spec-6fe394"></a>• [`description_spec`](#spec-6fe394) - Optional String<br>Description. Human readable description
|
|
211
|
+
|
|
212
|
+
<a id="rules-egress-rules-metadata-name"></a>• [`name`](#rules-egress-rules-metadata-name) - Optional String<br>Name of the message. The value of name has to follow DNS-1035 format
|
|
213
|
+
|
|
214
|
+
#### Rules Egress Rules Prefix List
|
|
215
|
+
|
|
216
|
+
A [`prefix_list`](#rules-egress-rules-prefix-list) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
217
|
+
|
|
218
|
+
<a id="rules-egress-rules-prefix-list-prefixes"></a>• [`prefixes`](#rules-egress-rules-prefix-list-prefixes) - Optional List<br>List of IPv4 prefixes that represent an endpoint
|
|
219
|
+
|
|
220
|
+
#### Rules Egress Rules Protocol Port Range
|
|
221
|
+
|
|
222
|
+
A [`protocol_port_range`](#rules-egress-rules-protocol-port-range) block (within [`rules.egress_rules`](#rules-egress-rules)) supports the following:
|
|
223
|
+
|
|
224
|
+
<a id="ranges-ffb05a"></a>• [`port_ranges`](#ranges-ffb05a) - Optional List<br>List of port ranges. Each range is a single port or a pair of start and end ports e.g. 8080-8192
|
|
225
|
+
|
|
226
|
+
<a id="protocol-77c4d7"></a>• [`protocol`](#protocol-77c4d7) - Optional String<br>Protocol in IP packet to be used as match criteria Values are TCP, UDP, and ICMP
|
|
227
|
+
|
|
228
|
+
#### Rules Ingress Rules
|
|
229
|
+
|
|
230
|
+
An [`ingress_rules`](#rules-ingress-rules) block (within [`rules`](#rules)) supports the following:
|
|
231
|
+
|
|
232
|
+
<a id="rules-ingress-rules-action"></a>• [`action`](#rules-ingress-rules-action) - Optional String Defaults to `DENY`<br>Possible values are `DENY`, `ALLOW`<br>[Enum: DENY|ALLOW] Network policy rule action configures the action to be taken on rule match Apply deny action on rule match Apply allow action on rule match
|
|
233
|
+
|
|
234
|
+
<a id="rules-ingress-rules-adv-action"></a>• [`adv_action`](#rules-ingress-rules-adv-action) - Optional Block<br>Network Policy Rule Advanced Action provides additional OPTIONS along with RuleAction and PBRRuleAction<br>See [Adv Action](#rules-ingress-rules-adv-action) below.
|
|
235
|
+
|
|
236
|
+
<a id="rules-ingress-rules-all-tcp-traffic"></a>• [`all_tcp_traffic`](#rules-ingress-rules-all-tcp-traffic) - Optional Block<br>Enable this option
|
|
237
|
+
|
|
238
|
+
<a id="rules-ingress-rules-all-traffic"></a>• [`all_traffic`](#rules-ingress-rules-all-traffic) - Optional Block<br>Enable this option
|
|
239
|
+
|
|
240
|
+
<a id="rules-ingress-rules-all-udp-traffic"></a>• [`all_udp_traffic`](#rules-ingress-rules-all-udp-traffic) - Optional Block<br>Enable this option
|
|
241
|
+
|
|
242
|
+
<a id="rules-ingress-rules-any"></a>• [`any`](#rules-ingress-rules-any) - Optional Block<br>Enable this option
|
|
243
|
+
|
|
244
|
+
<a id="rules-ingress-rules-applications"></a>• [`applications`](#rules-ingress-rules-applications) - Optional Block<br>Applications. Application protocols like HTTP, SNMP<br>See [Applications](#rules-ingress-rules-applications) below.
|
|
245
|
+
|
|
246
|
+
<a id="rules-ingress-rules-inside-endpoints"></a>• [`inside_endpoints`](#rules-ingress-rules-inside-endpoints) - Optional Block<br>Enable this option
|
|
247
|
+
|
|
248
|
+
<a id="rules-ingress-rules-ip-prefix-set"></a>• [`ip_prefix_set`](#rules-ingress-rules-ip-prefix-set) - Optional Block<br>List of references to ip_prefix_set objects<br>See [IP Prefix Set](#rules-ingress-rules-ip-prefix-set) below.
|
|
249
|
+
|
|
250
|
+
<a id="rules-ingress-rules-label-matcher"></a>• [`label_matcher`](#rules-ingress-rules-label-matcher) - Optional Block<br>Label matcher specifies a list of label keys whose values need to match for source/client and destination/server. Note that the actual label values are not specified and do not matter. This allows an ability to scope grouping by the label key name<br>See [Label Matcher](#rules-ingress-rules-label-matcher) below.
|
|
251
|
+
|
|
252
|
+
<a id="rules-ingress-rules-label-selector"></a>• [`label_selector`](#rules-ingress-rules-label-selector) - Optional Block<br>Type can be used to establish a 'selector reference' from one object(called selector) to a set of other objects(called selectees) based on the value of expresssions. A label selector is a label query over a set of resources. An empty label selector matches all objects<br>See [Label Selector](#rules-ingress-rules-label-selector) below.
|
|
253
|
+
|
|
254
|
+
<a id="rules-ingress-rules-metadata"></a>• [`metadata`](#rules-ingress-rules-metadata) - Optional Block<br>MessageMetaType is metadata (common attributes) of a message that only certain messages have. This information is propagated to the metadata of a child object that gets created from the containing message during view processing. The information in this type can be specified by user during create<br>See [Metadata](#rules-ingress-rules-metadata) below.
|
|
255
|
+
|
|
256
|
+
<a id="rules-ingress-rules-outside-endpoints"></a>• [`outside_endpoints`](#rules-ingress-rules-outside-endpoints) - Optional Block<br>Enable this option
|
|
257
|
+
|
|
258
|
+
<a id="rules-ingress-rules-prefix-list"></a>• [`prefix_list`](#rules-ingress-rules-prefix-list) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Prefix List](#rules-ingress-rules-prefix-list) below.
|
|
259
|
+
|
|
260
|
+
<a id="rules-ingress-rules-protocol-port-range"></a>• [`protocol_port_range`](#rules-ingress-rules-protocol-port-range) - Optional Block<br>Protocol and Port. Protocol and Port ranges<br>See [Protocol Port Range](#rules-ingress-rules-protocol-port-range) below.
|
|
261
|
+
|
|
262
|
+
#### Rules Ingress Rules Adv Action
|
|
263
|
+
|
|
264
|
+
An [`adv_action`](#rules-ingress-rules-adv-action) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
265
|
+
|
|
266
|
+
<a id="rules-ingress-rules-adv-action-action"></a>• [`action`](#rules-ingress-rules-adv-action-action) - Optional String Defaults to `NOLOG`<br>Possible values are `NOLOG`, `LOG`<br>[Enum: NOLOG|LOG] Choice to choose logging or no logging This works together with option selected via NetworkPolicyRuleAction or any other action specified x-
|
|
267
|
+
|
|
268
|
+
#### Rules Ingress Rules Applications
|
|
269
|
+
|
|
270
|
+
An [`applications`](#rules-ingress-rules-applications) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
271
|
+
|
|
272
|
+
<a id="applications-ada048"></a>• [`applications`](#applications-ada048) - Optional List Defaults to `APPLICATION_HTTP`<br>Possible values are `APPLICATION_HTTP`, `APPLICATION_HTTPS`, `APPLICATION_SNMP`, `APPLICATION_DNS`<br>[Enum: APPLICATION_HTTP|APPLICATION_HTTPS|APPLICATION_SNMP|APPLICATION_DNS] Application Protocols. Application protocols like HTTP, SNMP
|
|
273
|
+
|
|
274
|
+
#### Rules Ingress Rules IP Prefix Set
|
|
275
|
+
|
|
276
|
+
An [`ip_prefix_set`](#rules-ingress-rules-ip-prefix-set) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
277
|
+
|
|
278
|
+
<a id="rules-ingress-rules-ip-prefix-set-ref"></a>• [`ref`](#rules-ingress-rules-ip-prefix-set-ref) - Optional Block<br>List of references to ip_prefix_set objects<br>See [Ref](#rules-ingress-rules-ip-prefix-set-ref) below.
|
|
279
|
+
|
|
280
|
+
#### Rules Ingress Rules IP Prefix Set Ref
|
|
281
|
+
|
|
282
|
+
A [`ref`](#rules-ingress-rules-ip-prefix-set-ref) block (within [`rules.ingress_rules.ip_prefix_set`](#rules-ingress-rules-ip-prefix-set)) supports the following:
|
|
283
|
+
|
|
284
|
+
<a id="kind-3a83c1"></a>• [`kind`](#kind-3a83c1) - 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')
|
|
106
285
|
|
|
107
|
-
|
|
286
|
+
<a id="name-c9035f"></a>• [`name`](#name-c9035f) - 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
|
|
108
287
|
|
|
109
|
-
<a id="
|
|
288
|
+
<a id="namespace-0b6e5e"></a>• [`namespace`](#namespace-0b6e5e) - 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
|
|
110
289
|
|
|
111
|
-
|
|
290
|
+
<a id="tenant-b81c73"></a>• [`tenant`](#tenant-b81c73) - 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
|
|
112
291
|
|
|
113
|
-
|
|
292
|
+
<a id="uid-0be2c4"></a>• [`uid`](#uid-0be2c4) - 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
|
|
114
293
|
|
|
115
|
-
|
|
294
|
+
#### Rules Ingress Rules Label Matcher
|
|
116
295
|
|
|
117
|
-
|
|
296
|
+
A [`label_matcher`](#rules-ingress-rules-label-matcher) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
118
297
|
|
|
119
|
-
|
|
298
|
+
<a id="rules-ingress-rules-label-matcher-keys"></a>• [`keys`](#rules-ingress-rules-label-matcher-keys) - Optional List<br>The list of label key names that have to match
|
|
120
299
|
|
|
121
|
-
|
|
300
|
+
#### Rules Ingress Rules Label Selector
|
|
122
301
|
|
|
123
|
-
|
|
302
|
+
A [`label_selector`](#rules-ingress-rules-label-selector) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
124
303
|
|
|
125
|
-
<a id="
|
|
304
|
+
<a id="expressions-151d69"></a>• [`expressions`](#expressions-151d69) - Optional List<br>Expressions contains the Kubernetes style label expression for selections
|
|
126
305
|
|
|
127
|
-
|
|
306
|
+
#### Rules Ingress Rules Metadata
|
|
128
307
|
|
|
129
|
-
|
|
308
|
+
A [`metadata`](#rules-ingress-rules-metadata) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
130
309
|
|
|
131
|
-
|
|
310
|
+
<a id="spec-3d4978"></a>• [`description_spec`](#spec-3d4978) - Optional String<br>Description. Human readable description
|
|
132
311
|
|
|
133
|
-
|
|
312
|
+
<a id="rules-ingress-rules-metadata-name"></a>• [`name`](#rules-ingress-rules-metadata-name) - Optional String<br>Name of the message. The value of name has to follow DNS-1035 format
|
|
134
313
|
|
|
135
|
-
|
|
314
|
+
#### Rules Ingress Rules Prefix List
|
|
136
315
|
|
|
137
|
-
|
|
316
|
+
A [`prefix_list`](#rules-ingress-rules-prefix-list) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
138
317
|
|
|
139
|
-
|
|
318
|
+
<a id="prefixes-89e9a7"></a>• [`prefixes`](#prefixes-89e9a7) - Optional List<br>List of IPv4 prefixes that represent an endpoint
|
|
140
319
|
|
|
141
|
-
|
|
320
|
+
#### Rules Ingress Rules Protocol Port Range
|
|
142
321
|
|
|
143
|
-
|
|
322
|
+
A [`protocol_port_range`](#rules-ingress-rules-protocol-port-range) block (within [`rules.ingress_rules`](#rules-ingress-rules)) supports the following:
|
|
144
323
|
|
|
145
|
-
|
|
324
|
+
<a id="ranges-86d162"></a>• [`port_ranges`](#ranges-86d162) - Optional List<br>List of port ranges. Each range is a single port or a pair of start and end ports e.g. 8080-8192
|
|
146
325
|
|
|
147
|
-
<a id="
|
|
326
|
+
<a id="protocol-a45394"></a>• [`protocol`](#protocol-a45394) - Optional String<br>Protocol in IP packet to be used as match criteria Values are TCP, UDP, and ICMP
|
|
148
327
|
|
|
149
328
|
#### Timeouts
|
|
150
329
|
|
|
@@ -40,7 +40,7 @@ resource "f5xc_network_policy_view" "example" {
|
|
|
40
40
|
adv_action {
|
|
41
41
|
# Configure adv_action settings
|
|
42
42
|
}
|
|
43
|
-
#
|
|
43
|
+
# Enable this option
|
|
44
44
|
all_tcp_traffic {
|
|
45
45
|
# Configure all_tcp_traffic settings
|
|
46
46
|
}
|
|
@@ -90,17 +90,17 @@ An [`egress_rules`](#egress-rules) block supports the following:
|
|
|
90
90
|
|
|
91
91
|
<a id="egress-rules-adv-action"></a>• [`adv_action`](#egress-rules-adv-action) - Optional Block<br>Network Policy Rule Advanced Action provides additional OPTIONS along with RuleAction and PBRRuleAction<br>See [Adv Action](#egress-rules-adv-action) below.
|
|
92
92
|
|
|
93
|
-
<a id="egress-rules-all-tcp-traffic"></a>• [`all_tcp_traffic`](#egress-rules-all-tcp-traffic) - Optional Block<br>
|
|
93
|
+
<a id="egress-rules-all-tcp-traffic"></a>• [`all_tcp_traffic`](#egress-rules-all-tcp-traffic) - Optional Block<br>Enable this option
|
|
94
94
|
|
|
95
|
-
<a id="egress-rules-all-traffic"></a>• [`all_traffic`](#egress-rules-all-traffic) - Optional Block<br>
|
|
95
|
+
<a id="egress-rules-all-traffic"></a>• [`all_traffic`](#egress-rules-all-traffic) - Optional Block<br>Enable this option
|
|
96
96
|
|
|
97
|
-
<a id="egress-rules-all-udp-traffic"></a>• [`all_udp_traffic`](#egress-rules-all-udp-traffic) - Optional Block<br>
|
|
97
|
+
<a id="egress-rules-all-udp-traffic"></a>• [`all_udp_traffic`](#egress-rules-all-udp-traffic) - Optional Block<br>Enable this option
|
|
98
98
|
|
|
99
|
-
<a id="egress-rules-any"></a>• [`any`](#egress-rules-any) - Optional Block<br>
|
|
99
|
+
<a id="egress-rules-any"></a>• [`any`](#egress-rules-any) - Optional Block<br>Enable this option
|
|
100
100
|
|
|
101
101
|
<a id="egress-rules-applications"></a>• [`applications`](#egress-rules-applications) - Optional Block<br>Applications. Application protocols like HTTP, SNMP<br>See [Applications](#egress-rules-applications) below.
|
|
102
102
|
|
|
103
|
-
<a id="egress-rules-inside-endpoints"></a>• [`inside_endpoints`](#egress-rules-inside-endpoints) - Optional Block<br>
|
|
103
|
+
<a id="egress-rules-inside-endpoints"></a>• [`inside_endpoints`](#egress-rules-inside-endpoints) - Optional Block<br>Enable this option
|
|
104
104
|
|
|
105
105
|
<a id="egress-rules-ip-prefix-set"></a>• [`ip_prefix_set`](#egress-rules-ip-prefix-set) - Optional Block<br>List of references to ip_prefix_set objects<br>See [IP Prefix Set](#egress-rules-ip-prefix-set) below.
|
|
106
106
|
|
|
@@ -110,7 +110,7 @@ An [`egress_rules`](#egress-rules) block supports the following:
|
|
|
110
110
|
|
|
111
111
|
<a id="egress-rules-metadata"></a>• [`metadata`](#egress-rules-metadata) - Optional Block<br>MessageMetaType is metadata (common attributes) of a message that only certain messages have. This information is propagated to the metadata of a child object that gets created from the containing message during view processing. The information in this type can be specified by user during create<br>See [Metadata](#egress-rules-metadata) below.
|
|
112
112
|
|
|
113
|
-
<a id="egress-rules-outside-endpoints"></a>• [`outside_endpoints`](#egress-rules-outside-endpoints) - Optional Block<br>
|
|
113
|
+
<a id="egress-rules-outside-endpoints"></a>• [`outside_endpoints`](#egress-rules-outside-endpoints) - Optional Block<br>Enable this option
|
|
114
114
|
|
|
115
115
|
<a id="egress-rules-prefix-list"></a>• [`prefix_list`](#egress-rules-prefix-list) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Prefix List](#egress-rules-prefix-list) below.
|
|
116
116
|
|
|
@@ -186,13 +186,13 @@ A [`protocol_port_range`](#egress-rules-protocol-port-range) block (within [`egr
|
|
|
186
186
|
|
|
187
187
|
An [`endpoint`](#endpoint) block supports the following:
|
|
188
188
|
|
|
189
|
-
<a id="endpoint-any"></a>• [`any`](#endpoint-any) - Optional Block<br>
|
|
189
|
+
<a id="endpoint-any"></a>• [`any`](#endpoint-any) - Optional Block<br>Enable this option
|
|
190
190
|
|
|
191
|
-
<a id="endpoint-inside-endpoints"></a>• [`inside_endpoints`](#endpoint-inside-endpoints) - Optional Block<br>
|
|
191
|
+
<a id="endpoint-inside-endpoints"></a>• [`inside_endpoints`](#endpoint-inside-endpoints) - Optional Block<br>Enable this option
|
|
192
192
|
|
|
193
193
|
<a id="endpoint-label-selector"></a>• [`label_selector`](#endpoint-label-selector) - Optional Block<br>Type can be used to establish a 'selector reference' from one object(called selector) to a set of other objects(called selectees) based on the value of expresssions. A label selector is a label query over a set of resources. An empty label selector matches all objects<br>See [Label Selector](#endpoint-label-selector) below.
|
|
194
194
|
|
|
195
|
-
<a id="endpoint-outside-endpoints"></a>• [`outside_endpoints`](#endpoint-outside-endpoints) - Optional Block<br>
|
|
195
|
+
<a id="endpoint-outside-endpoints"></a>• [`outside_endpoints`](#endpoint-outside-endpoints) - Optional Block<br>Enable this option
|
|
196
196
|
|
|
197
197
|
<a id="endpoint-prefix-list"></a>• [`prefix_list`](#endpoint-prefix-list) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Prefix List](#endpoint-prefix-list) below.
|
|
198
198
|
|
|
@@ -216,17 +216,17 @@ An [`ingress_rules`](#ingress-rules) block supports the following:
|
|
|
216
216
|
|
|
217
217
|
<a id="ingress-rules-adv-action"></a>• [`adv_action`](#ingress-rules-adv-action) - Optional Block<br>Network Policy Rule Advanced Action provides additional OPTIONS along with RuleAction and PBRRuleAction<br>See [Adv Action](#ingress-rules-adv-action) below.
|
|
218
218
|
|
|
219
|
-
<a id="ingress-rules-all-tcp-traffic"></a>• [`all_tcp_traffic`](#ingress-rules-all-tcp-traffic) - Optional Block<br>
|
|
219
|
+
<a id="ingress-rules-all-tcp-traffic"></a>• [`all_tcp_traffic`](#ingress-rules-all-tcp-traffic) - Optional Block<br>Enable this option
|
|
220
220
|
|
|
221
|
-
<a id="ingress-rules-all-traffic"></a>• [`all_traffic`](#ingress-rules-all-traffic) - Optional Block<br>
|
|
221
|
+
<a id="ingress-rules-all-traffic"></a>• [`all_traffic`](#ingress-rules-all-traffic) - Optional Block<br>Enable this option
|
|
222
222
|
|
|
223
|
-
<a id="ingress-rules-all-udp-traffic"></a>• [`all_udp_traffic`](#ingress-rules-all-udp-traffic) - Optional Block<br>
|
|
223
|
+
<a id="ingress-rules-all-udp-traffic"></a>• [`all_udp_traffic`](#ingress-rules-all-udp-traffic) - Optional Block<br>Enable this option
|
|
224
224
|
|
|
225
|
-
<a id="ingress-rules-any"></a>• [`any`](#ingress-rules-any) - Optional Block<br>
|
|
225
|
+
<a id="ingress-rules-any"></a>• [`any`](#ingress-rules-any) - Optional Block<br>Enable this option
|
|
226
226
|
|
|
227
227
|
<a id="ingress-rules-applications"></a>• [`applications`](#ingress-rules-applications) - Optional Block<br>Applications. Application protocols like HTTP, SNMP<br>See [Applications](#ingress-rules-applications) below.
|
|
228
228
|
|
|
229
|
-
<a id="ingress-rules-inside-endpoints"></a>• [`inside_endpoints`](#ingress-rules-inside-endpoints) - Optional Block<br>
|
|
229
|
+
<a id="ingress-rules-inside-endpoints"></a>• [`inside_endpoints`](#ingress-rules-inside-endpoints) - Optional Block<br>Enable this option
|
|
230
230
|
|
|
231
231
|
<a id="ingress-rules-ip-prefix-set"></a>• [`ip_prefix_set`](#ingress-rules-ip-prefix-set) - Optional Block<br>List of references to ip_prefix_set objects<br>See [IP Prefix Set](#ingress-rules-ip-prefix-set) below.
|
|
232
232
|
|
|
@@ -236,7 +236,7 @@ An [`ingress_rules`](#ingress-rules) block supports the following:
|
|
|
236
236
|
|
|
237
237
|
<a id="ingress-rules-metadata"></a>• [`metadata`](#ingress-rules-metadata) - Optional Block<br>MessageMetaType is metadata (common attributes) of a message that only certain messages have. This information is propagated to the metadata of a child object that gets created from the containing message during view processing. The information in this type can be specified by user during create<br>See [Metadata](#ingress-rules-metadata) below.
|
|
238
238
|
|
|
239
|
-
<a id="ingress-rules-outside-endpoints"></a>• [`outside_endpoints`](#ingress-rules-outside-endpoints) - Optional Block<br>
|
|
239
|
+
<a id="ingress-rules-outside-endpoints"></a>• [`outside_endpoints`](#ingress-rules-outside-endpoints) - Optional Block<br>Enable this option
|
|
240
240
|
|
|
241
241
|
<a id="ingress-rules-prefix-list"></a>• [`prefix_list`](#ingress-rules-prefix-list) - Optional Block<br>List of IPv4 prefixes that represent an endpoint<br>See [Prefix List](#ingress-rules-prefix-list) below.
|
|
242
242
|
|
|
@@ -67,10 +67,10 @@ resource "f5xc_nfv_service" "example" {
|
|
|
67
67
|
### Spec Argument Reference
|
|
68
68
|
|
|
69
69
|
-> **One of the following:**
|
|
70
|
-
• <a id="disable-https-management"></a>[`disable_https_management`](#disable-https-management) - Optional Block<br>
|
|
70
|
+
• <a id="disable-https-management"></a>[`disable_https_management`](#disable-https-management) - Optional Block<br>Enable this option
|
|
71
71
|
|
|
72
72
|
-> **One of the following:**
|
|
73
|
-
• <a id="disable-ssh-access"></a>[`disable_ssh_access`](#disable-ssh-access) - Optional Block<br>
|
|
73
|
+
• <a id="disable-ssh-access"></a>[`disable_ssh_access`](#disable-ssh-access) - Optional Block<br>Enable this option
|
|
74
74
|
|
|
75
75
|
<a id="enabled-ssh-access"></a>• [`enabled_ssh_access`](#enabled-ssh-access) - Optional Block<br>SSH based management. SSH based configuration<br>See [Enabled SSH Access](#enabled-ssh-access) below for details.
|
|
76
76
|
|
|
@@ -94,11 +94,11 @@ In addition to all arguments above, the following attributes are exported:
|
|
|
94
94
|
|
|
95
95
|
An [`enabled_ssh_access`](#enabled-ssh-access) block supports the following:
|
|
96
96
|
|
|
97
|
-
<a id="enabled-ssh-access-advertise-on-sli"></a>• [`advertise_on_sli`](#enabled-ssh-access-advertise-on-sli) - Optional Block<br>
|
|
97
|
+
<a id="enabled-ssh-access-advertise-on-sli"></a>• [`advertise_on_sli`](#enabled-ssh-access-advertise-on-sli) - Optional Block<br>Enable this option
|
|
98
98
|
|
|
99
|
-
<a id="enabled-ssh-access-advertise-on-slo"></a>• [`advertise_on_slo`](#enabled-ssh-access-advertise-on-slo) - Optional Block<br>
|
|
99
|
+
<a id="enabled-ssh-access-advertise-on-slo"></a>• [`advertise_on_slo`](#enabled-ssh-access-advertise-on-slo) - Optional Block<br>Enable this option
|
|
100
100
|
|
|
101
|
-
<a id="enabled-ssh-access-advertise-on-slo-sli"></a>• [`advertise_on_slo_sli`](#enabled-ssh-access-advertise-on-slo-sli) - Optional Block<br>
|
|
101
|
+
<a id="enabled-ssh-access-advertise-on-slo-sli"></a>• [`advertise_on_slo_sli`](#enabled-ssh-access-advertise-on-slo-sli) - Optional Block<br>Enable this option
|
|
102
102
|
|
|
103
103
|
<a id="enabled-ssh-access-domain-suffix"></a>• [`domain_suffix`](#enabled-ssh-access-domain-suffix) - Optional String<br>Domain suffix will be used along with node name to form the hostname for SSH node management
|
|
104
104
|
|
|
@@ -160,11 +160,11 @@ An [`admin_password`](#f5-big-ip-aws-service-admin-password) block (within [`f5_
|
|
|
160
160
|
|
|
161
161
|
An [`endpoint_service`](#f5-big-ip-aws-service-endpoint-service) block (within [`f5_big_ip_aws_service`](#f5-big-ip-aws-service)) supports the following:
|
|
162
162
|
|
|
163
|
-
<a id="slo-ip-6fccc9"></a>• [`advertise_on_slo_ip`](#slo-ip-6fccc9) - Optional Block<br>
|
|
163
|
+
<a id="slo-ip-6fccc9"></a>• [`advertise_on_slo_ip`](#slo-ip-6fccc9) - Optional Block<br>Enable this option
|
|
164
164
|
|
|
165
|
-
<a id="external-c6878c"></a>• [`advertise_on_slo_ip_external`](#external-c6878c) - Optional Block<br>
|
|
165
|
+
<a id="external-c6878c"></a>• [`advertise_on_slo_ip_external`](#external-c6878c) - Optional Block<br>Enable this option
|
|
166
166
|
|
|
167
|
-
<a id="vip-bf0a34"></a>• [`automatic_vip`](#vip-bf0a34) - Optional Block<br>
|
|
167
|
+
<a id="vip-bf0a34"></a>• [`automatic_vip`](#vip-bf0a34) - Optional Block<br>Enable this option
|
|
168
168
|
|
|
169
169
|
<a id="vip-39201b"></a>• [`configured_vip`](#vip-39201b) - Optional String<br>Enter IP address for the default VIP
|
|
170
170
|
|
|
@@ -172,17 +172,17 @@ An [`endpoint_service`](#f5-big-ip-aws-service-endpoint-service) block (within [
|
|
|
172
172
|
|
|
173
173
|
<a id="ports-775f61"></a>• [`custom_udp_ports`](#ports-775f61) - Optional Block<br>Port Range List. List of port ranges<br>See [Custom UDP Ports](#ports-775f61) below.
|
|
174
174
|
|
|
175
|
-
<a id="ports-4442b0"></a>• [`default_tcp_ports`](#ports-4442b0) - Optional Block<br>
|
|
175
|
+
<a id="ports-4442b0"></a>• [`default_tcp_ports`](#ports-4442b0) - Optional Block<br>Enable this option
|
|
176
176
|
|
|
177
|
-
<a id="slo-ip-47bf10"></a>• [`disable_advertise_on_slo_ip`](#slo-ip-47bf10) - Optional Block<br>
|
|
177
|
+
<a id="slo-ip-47bf10"></a>• [`disable_advertise_on_slo_ip`](#slo-ip-47bf10) - Optional Block<br>Enable this option
|
|
178
178
|
|
|
179
|
-
<a id="port-926fe7"></a>• [`http_port`](#port-926fe7) - Optional Block<br>
|
|
179
|
+
<a id="port-926fe7"></a>• [`http_port`](#port-926fe7) - Optional Block<br>Enable this option
|
|
180
180
|
|
|
181
|
-
<a id="port-440dce"></a>• [`https_port`](#port-440dce) - Optional Block<br>
|
|
181
|
+
<a id="port-440dce"></a>• [`https_port`](#port-440dce) - Optional Block<br>Enable this option
|
|
182
182
|
|
|
183
|
-
<a id="ports-4d510f"></a>• [`no_tcp_ports`](#ports-4d510f) - Optional Block<br>
|
|
183
|
+
<a id="ports-4d510f"></a>• [`no_tcp_ports`](#ports-4d510f) - Optional Block<br>Enable this option
|
|
184
184
|
|
|
185
|
-
<a id="ports-abc1e4"></a>• [`no_udp_ports`](#ports-abc1e4) - Optional Block<br>
|
|
185
|
+
<a id="ports-abc1e4"></a>• [`no_udp_ports`](#ports-abc1e4) - Optional Block<br>Enable this option
|
|
186
186
|
|
|
187
187
|
#### F5 Big IP AWS Service Endpoint Service Custom TCP Ports
|
|
188
188
|
|
|
@@ -200,7 +200,7 @@ An [`endpoint_service`](#f5-big-ip-aws-service-endpoint-service) block (within [
|
|
|
200
200
|
|
|
201
201
|
A [`nodes`](#f5-big-ip-aws-service-nodes) block (within [`f5_big_ip_aws_service`](#f5-big-ip-aws-service)) supports the following:
|
|
202
202
|
|
|
203
|
-
<a id="prefix-e8faa8"></a>• [`automatic_prefix`](#prefix-e8faa8) - Optional Block<br>
|
|
203
|
+
<a id="prefix-e8faa8"></a>• [`automatic_prefix`](#prefix-e8faa8) - Optional Block<br>Enable this option
|
|
204
204
|
|
|
205
205
|
<a id="f5-big-ip-aws-service-nodes-aws-az-name"></a>• [`aws_az_name`](#f5-big-ip-aws-service-nodes-aws-az-name) - Optional String<br>The AWS Availability Zone must be consistent with the AWS Region chosen. Please select an AZ in the same Region as your TGW Site
|
|
206
206
|
|
|
@@ -208,7 +208,7 @@ A [`nodes`](#f5-big-ip-aws-service-nodes) block (within [`f5_big_ip_aws_service`
|
|
|
208
208
|
|
|
209
209
|
<a id="f5-big-ip-aws-service-nodes-node-name"></a>• [`node_name`](#f5-big-ip-aws-service-nodes-node-name) - Optional String<br>Node Name will be used to assign as hostname to the service
|
|
210
210
|
|
|
211
|
-
<a id="subnet-2782dc"></a>• [`reserved_mgmt_subnet`](#subnet-2782dc) - Optional Block<br>
|
|
211
|
+
<a id="subnet-2782dc"></a>• [`reserved_mgmt_subnet`](#subnet-2782dc) - Optional Block<br>Enable this option
|
|
212
212
|
|
|
213
213
|
<a id="prefix-53b238"></a>• [`tunnel_prefix`](#prefix-53b238) - Optional String<br>Enter IP prefix for the tunnel, it has to be /30
|
|
214
214
|
|
|
@@ -226,7 +226,7 @@ A [`https_management`](#https-management) block supports the following:
|
|
|
226
226
|
|
|
227
227
|
<a id="https-management-advertise-on-internet"></a>• [`advertise_on_internet`](#https-management-advertise-on-internet) - Optional Block<br>Defines a way to advertise a load balancer on public. If optional public_ip is provided, it will only be advertised on RE sites where that public_ip is available<br>See [Advertise On Internet](#https-management-advertise-on-internet) below.
|
|
228
228
|
|
|
229
|
-
<a id="vip-00de2c"></a>• [`advertise_on_internet_default_vip`](#vip-00de2c) - Optional Block<br>
|
|
229
|
+
<a id="vip-00de2c"></a>• [`advertise_on_internet_default_vip`](#vip-00de2c) - Optional Block<br>Enable this option
|
|
230
230
|
|
|
231
231
|
<a id="https-management-advertise-on-sli-vip"></a>• [`advertise_on_sli_vip`](#https-management-advertise-on-sli-vip) - Optional Block<br>Inline TLS Parameters. Inline TLS parameters<br>See [Advertise On SLI VIP](#https-management-advertise-on-sli-vip) below.
|
|
232
232
|
|
|
@@ -236,7 +236,7 @@ A [`https_management`](#https-management) block supports the following:
|
|
|
236
236
|
|
|
237
237
|
<a id="https-management-advertise-on-slo-vip"></a>• [`advertise_on_slo_vip`](#https-management-advertise-on-slo-vip) - Optional Block<br>Inline TLS Parameters. Inline TLS parameters<br>See [Advertise On Slo VIP](#https-management-advertise-on-slo-vip) below.
|
|
238
238
|
|
|
239
|
-
<a id="https-management-default-https-port"></a>• [`default_https_port`](#https-management-default-https-port) - Optional Block<br>
|
|
239
|
+
<a id="https-management-default-https-port"></a>• [`default_https_port`](#https-management-default-https-port) - Optional Block<br>Enable this option
|
|
240
240
|
|
|
241
241
|
<a id="https-management-domain-suffix"></a>• [`domain_suffix`](#https-management-domain-suffix) - Optional String<br>Domain suffix will be used along with node name to form URL to access node management
|
|
242
242
|
|
|
@@ -262,7 +262,7 @@ A [`public_ip`](#public-ip-e501cc) block (within [`https_management.advertise_on
|
|
|
262
262
|
|
|
263
263
|
An [`advertise_on_sli_vip`](#https-management-advertise-on-sli-vip) block (within [`https_management`](#https-management)) supports the following:
|
|
264
264
|
|
|
265
|
-
<a id="mtls-1bd8e3"></a>• [`no_mtls`](#mtls-1bd8e3) - Optional Block<br>
|
|
265
|
+
<a id="mtls-1bd8e3"></a>• [`no_mtls`](#mtls-1bd8e3) - Optional Block<br>Enable this option
|
|
266
266
|
|
|
267
267
|
<a id="certificates-5355d7"></a>• [`tls_certificates`](#certificates-5355d7) - Optional Block<br>Users can add one or more certificates that share the same set of domains. For example, domain.com and \*.domain.com - but use different signature algorithms<br>See [TLS Certificates](#certificates-5355d7) below.
|
|
268
268
|
|
|
@@ -318,7 +318,7 @@ An [`advertise_on_sli_vip`](#https-management-advertise-on-sli-vip) block (withi
|
|
|
318
318
|
|
|
319
319
|
An [`advertise_on_slo_internet_vip`](#vip-6dd6e5) block (within [`https_management`](#https-management)) supports the following:
|
|
320
320
|
|
|
321
|
-
<a id="mtls-65c4ed"></a>• [`no_mtls`](#mtls-65c4ed) - Optional Block<br>
|
|
321
|
+
<a id="mtls-65c4ed"></a>• [`no_mtls`](#mtls-65c4ed) - Optional Block<br>Enable this option
|
|
322
322
|
|
|
323
323
|
<a id="certificates-748bff"></a>• [`tls_certificates`](#certificates-748bff) - Optional Block<br>Users can add one or more certificates that share the same set of domains. For example, domain.com and \*.domain.com - but use different signature algorithms<br>See [TLS Certificates](#certificates-748bff) below.
|
|
324
324
|
|
|
@@ -374,7 +374,7 @@ An [`advertise_on_slo_internet_vip`](#vip-6dd6e5) block (within [`https_manageme
|
|
|
374
374
|
|
|
375
375
|
An [`advertise_on_slo_sli`](#https-management-advertise-on-slo-sli) block (within [`https_management`](#https-management)) supports the following:
|
|
376
376
|
|
|
377
|
-
<a id="mtls-e2f684"></a>• [`no_mtls`](#mtls-e2f684) - Optional Block<br>
|
|
377
|
+
<a id="mtls-e2f684"></a>• [`no_mtls`](#mtls-e2f684) - Optional Block<br>Enable this option
|
|
378
378
|
|
|
379
379
|
<a id="certificates-b923c1"></a>• [`tls_certificates`](#certificates-b923c1) - Optional Block<br>Users can add one or more certificates that share the same set of domains. For example, domain.com and \*.domain.com - but use different signature algorithms<br>See [TLS Certificates](#certificates-b923c1) below.
|
|
380
380
|
|
|
@@ -430,7 +430,7 @@ An [`advertise_on_slo_sli`](#https-management-advertise-on-slo-sli) block (withi
|
|
|
430
430
|
|
|
431
431
|
An [`advertise_on_slo_vip`](#https-management-advertise-on-slo-vip) block (within [`https_management`](#https-management)) supports the following:
|
|
432
432
|
|
|
433
|
-
<a id="mtls-476751"></a>• [`no_mtls`](#mtls-476751) - Optional Block<br>
|
|
433
|
+
<a id="mtls-476751"></a>• [`no_mtls`](#mtls-476751) - Optional Block<br>Enable this option
|
|
434
434
|
|
|
435
435
|
<a id="certificates-49cf23"></a>• [`tls_certificates`](#certificates-49cf23) - Optional Block<br>Users can add one or more certificates that share the same set of domains. For example, domain.com and \*.domain.com - but use different signature algorithms<br>See [TLS Certificates](#certificates-49cf23) below.
|
|
436
436
|
|
|
@@ -490,13 +490,13 @@ A [`palo_alto_fw_service`](#palo-alto-fw-service) block supports the following:
|
|
|
490
490
|
|
|
491
491
|
<a id="palo-alto-fw-service-aws-tgw-site"></a>• [`aws_tgw_site`](#palo-alto-fw-service-aws-tgw-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 [AWS TGW Site](#palo-alto-fw-service-aws-tgw-site) below.
|
|
492
492
|
|
|
493
|
-
<a id="palo-alto-fw-service-disable-panaroma"></a>• [`disable_panaroma`](#palo-alto-fw-service-disable-panaroma) - Optional Block<br>
|
|
493
|
+
<a id="palo-alto-fw-service-disable-panaroma"></a>• [`disable_panaroma`](#palo-alto-fw-service-disable-panaroma) - Optional Block<br>Enable this option
|
|
494
494
|
|
|
495
495
|
<a id="palo-alto-fw-service-instance-type"></a>• [`instance_type`](#palo-alto-fw-service-instance-type) - Optional String Defaults to `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_XLARGE`<br>Possible values are `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_2XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_4XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_LARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_2XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_4XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_12XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_LARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_2XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_4XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_LARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_2XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_4XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_8XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_LARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_2XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_4XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_9XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_18XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_LARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_2XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_4XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_9XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_18XLARGE`, `PALO_ALTO_FW_AWS_INSTANCE_TYPE_R5_2XLARGE`<br>[Enum: PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_2XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_4XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_LARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_2XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_4XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_12XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_LARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_2XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5N_4XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_LARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_2XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_4XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C4_8XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_LARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_2XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_4XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_9XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5_18XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_LARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_2XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_4XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_9XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_C5N_18XLARGE|PALO_ALTO_FW_AWS_INSTANCE_TYPE_R5_2XLARGE] - PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_XLARGE: m4.xlarge - PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_2XLARGE: m4.2xlarge - PALO_ALTO_FW_AWS_INSTANCE_TYPE_M4_4XLARGE: m4.4xlarge - PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_LARGE: m5.large - PALO_ALTO_FW_AWS_INSTANCE_TYPE_M5_XLARGE: m5.xlarge
|
|
496
496
|
|
|
497
|
-
<a id="palo-alto-fw-service-pan-ami-bundle1"></a>• [`pan_ami_bundle1`](#palo-alto-fw-service-pan-ami-bundle1) - Optional Block<br>
|
|
497
|
+
<a id="palo-alto-fw-service-pan-ami-bundle1"></a>• [`pan_ami_bundle1`](#palo-alto-fw-service-pan-ami-bundle1) - Optional Block<br>Enable this option
|
|
498
498
|
|
|
499
|
-
<a id="palo-alto-fw-service-pan-ami-bundle2"></a>• [`pan_ami_bundle2`](#palo-alto-fw-service-pan-ami-bundle2) - Optional Block<br>
|
|
499
|
+
<a id="palo-alto-fw-service-pan-ami-bundle2"></a>• [`pan_ami_bundle2`](#palo-alto-fw-service-pan-ami-bundle2) - Optional Block<br>Enable this option
|
|
500
500
|
|
|
501
501
|
<a id="palo-alto-fw-service-panorama-server"></a>• [`panorama_server`](#palo-alto-fw-service-panorama-server) - Optional Block<br>Panorama Server Type. Panorama Server Type<br>See [Panorama Server](#palo-alto-fw-service-panorama-server) below.
|
|
502
502
|
|
|
@@ -596,7 +596,7 @@ A [`nodes`](#nodes-b8137e) block (within [`palo_alto_fw_service.service_nodes`](
|
|
|
596
596
|
|
|
597
597
|
<a id="name-6e2eb6"></a>• [`node_name`](#name-6e2eb6) - Optional String<br>Node Name will be used to assign as hostname to the service
|
|
598
598
|
|
|
599
|
-
<a id="subnet-52b5ce"></a>• [`reserved_mgmt_subnet`](#subnet-52b5ce) - Optional Block<br>
|
|
599
|
+
<a id="subnet-52b5ce"></a>• [`reserved_mgmt_subnet`](#subnet-52b5ce) - Optional Block<br>Enable this option
|
|
600
600
|
|
|
601
601
|
#### Palo Alto Fw Service Service Nodes Nodes Mgmt Subnet
|
|
602
602
|
|