@robinmordasiewicz/f5xc-terraform-mcp 2.4.6 → 2.4.7
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/resources/addon_subscription.md +5 -5
- package/dist/docs/resources/address_allocator.md +3 -3
- package/dist/docs/resources/advertise_policy.md +39 -39
- package/dist/docs/resources/alert_policy.md +6 -6
- package/dist/docs/resources/alert_receiver.md +57 -57
- package/dist/docs/resources/api_crawler.md +9 -9
- package/dist/docs/resources/api_testing.md +40 -40
- package/dist/docs/resources/apm.md +320 -320
- package/dist/docs/resources/app_api_group.md +10 -10
- package/dist/docs/resources/app_firewall.md +36 -36
- package/dist/docs/resources/app_setting.md +46 -46
- package/dist/docs/resources/app_type.md +3 -3
- package/dist/docs/resources/authentication.md +30 -30
- package/dist/docs/resources/aws_tgw_site.md +184 -184
- package/dist/docs/resources/aws_vpc_site.md +296 -296
- package/dist/docs/resources/azure_vnet_site.md +677 -677
- package/dist/docs/resources/bgp.md +20 -20
- package/dist/docs/resources/bgp_routing_policy.md +4 -4
- package/dist/docs/resources/cdn_cache_rule.md +68 -68
- package/dist/docs/resources/cdn_loadbalancer.md +1166 -1166
- package/dist/docs/resources/certificate.md +4 -4
- package/dist/docs/resources/child_tenant.md +2 -2
- package/dist/docs/resources/cloud_connect.md +33 -33
- package/dist/docs/resources/cloud_credentials.md +37 -37
- package/dist/docs/resources/cloud_link.md +16 -16
- package/dist/docs/resources/cluster.md +68 -68
- package/dist/docs/resources/cminstance.md +6 -6
- package/dist/docs/resources/code_base_integration.md +82 -82
- package/dist/docs/resources/container_registry.md +2 -2
- package/dist/docs/resources/data_type.md +12 -12
- package/dist/docs/resources/discovery.md +71 -71
- package/dist/docs/resources/dns_lb_health_check.md +5 -5
- package/dist/docs/resources/dns_load_balancer.md +25 -25
- package/dist/docs/resources/dns_zone.md +144 -144
- package/dist/docs/resources/endpoint.md +1 -1
- package/dist/docs/resources/enhanced_firewall_policy.md +33 -33
- package/dist/docs/resources/external_connector.md +32 -32
- package/dist/docs/resources/fast_acl.md +59 -59
- package/dist/docs/resources/fast_acl_rule.md +2 -2
- package/dist/docs/resources/filter_set.md +3 -3
- package/dist/docs/resources/fleet.md +359 -359
- package/dist/docs/resources/forward_proxy_policy.md +18 -18
- package/dist/docs/resources/gcp_vpc_site.md +280 -280
- package/dist/docs/resources/geo_location_set.md +1 -1
- package/dist/docs/resources/global_log_receiver.md +216 -216
- package/dist/docs/resources/healthcheck.md +2 -2
- package/dist/docs/resources/http_loadbalancer.md +2190 -2190
- package/dist/docs/resources/infraprotect_tunnel.md +9 -9
- package/dist/docs/resources/k8s_cluster.md +39 -39
- package/dist/docs/resources/k8s_cluster_role.md +10 -10
- package/dist/docs/resources/k8s_pod_security_policy.md +9 -9
- package/dist/docs/resources/log_receiver.md +11 -11
- package/dist/docs/resources/malicious_user_mitigation.md +4 -4
- package/dist/docs/resources/managed_tenant.md +2 -2
- package/dist/docs/resources/nat_policy.md +22 -22
- package/dist/docs/resources/network_connector.md +37 -37
- package/dist/docs/resources/network_firewall.md +15 -15
- package/dist/docs/resources/network_interface.md +78 -78
- package/dist/docs/resources/network_policy.md +21 -21
- package/dist/docs/resources/network_policy_view.md +7 -7
- package/dist/docs/resources/nfv_service.md +306 -306
- package/dist/docs/resources/oidc_provider.md +1 -1
- package/dist/docs/resources/origin_pool.md +151 -151
- package/dist/docs/resources/policy_based_routing.md +71 -71
- package/dist/docs/resources/protocol_inspection.md +8 -8
- package/dist/docs/resources/proxy.md +401 -401
- package/dist/docs/resources/rate_limiter_policy.md +4 -4
- package/dist/docs/resources/registration.md +1 -1
- package/dist/docs/resources/route.md +155 -155
- package/dist/docs/resources/secret_management_access.md +103 -103
- package/dist/docs/resources/secret_policy.md +7 -7
- package/dist/docs/resources/securemesh_site.md +274 -274
- package/dist/docs/resources/securemesh_site_v2.md +940 -940
- package/dist/docs/resources/sensitive_data_policy.md +3 -3
- package/dist/docs/resources/service_policy.md +154 -154
- package/dist/docs/resources/service_policy_rule.md +51 -51
- package/dist/docs/resources/subnet.md +7 -7
- package/dist/docs/resources/tcp_loadbalancer.md +138 -138
- package/dist/docs/resources/tenant_configuration.md +1 -1
- package/dist/docs/resources/ticket_tracking_system.md +2 -2
- package/dist/docs/resources/tunnel.md +16 -16
- package/dist/docs/resources/udp_loadbalancer.md +56 -56
- package/dist/docs/resources/virtual_host.md +146 -146
- package/dist/docs/resources/virtual_network.md +7 -7
- package/dist/docs/resources/voltshare_admin_policy.md +22 -22
- package/dist/docs/resources/voltstack_site.md +778 -778
- package/dist/docs/resources/waf_exclusion_policy.md +22 -22
- package/dist/docs/resources/workload.md +2226 -2226
- package/package.json +1 -1
|
@@ -110,17 +110,17 @@ A [`private_key`](#private-key) block supports the following:
|
|
|
110
110
|
|
|
111
111
|
A [`blindfold_secret_info`](#private-key-blindfold-secret-info) block (within [`private_key`](#private-key)) supports the following:
|
|
112
112
|
|
|
113
|
-
<a id="
|
|
113
|
+
<a id="provider-2cb137"></a>• [`decryption_provider`](#provider-2cb137) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
|
|
114
114
|
|
|
115
|
-
<a id="
|
|
115
|
+
<a id="location-208dea"></a>• [`location`](#location-208dea) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
|
|
116
116
|
|
|
117
|
-
<a id="
|
|
117
|
+
<a id="provider-1e06e0"></a>• [`store_provider`](#provider-1e06e0) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
118
118
|
|
|
119
119
|
#### Private Key Clear Secret Info
|
|
120
120
|
|
|
121
121
|
A [`clear_secret_info`](#private-key-clear-secret-info) block (within [`private_key`](#private-key)) supports the following:
|
|
122
122
|
|
|
123
|
-
<a id="
|
|
123
|
+
<a id="ref-e799a7"></a>• [`provider_ref`](#ref-e799a7) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
124
124
|
|
|
125
125
|
<a id="private-key-clear-secret-info-url"></a>• [`url`](#private-key-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
|
|
126
126
|
|
|
@@ -54,6 +54,8 @@ resource "f5xc_child_tenant" "example" {
|
|
|
54
54
|
|
|
55
55
|
<a id="name"></a>• [`name`](#name) - Required String<br>Name of the Child Tenant. Must be unique within the namespace
|
|
56
56
|
|
|
57
|
+
<a id="namespace"></a>• [`namespace`](#namespace) - Required String<br>Namespace where the Child Tenant will be created
|
|
58
|
+
|
|
57
59
|
<a id="annotations"></a>• [`annotations`](#annotations) - Optional Map<br>Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata
|
|
58
60
|
|
|
59
61
|
<a id="description"></a>• [`description`](#description) - Optional String<br>Human readable description for the object
|
|
@@ -62,8 +64,6 @@ resource "f5xc_child_tenant" "example" {
|
|
|
62
64
|
|
|
63
65
|
<a id="labels"></a>• [`labels`](#labels) - Optional Map<br>Labels is a user defined key value map that can be attached to resources for organization and filtering
|
|
64
66
|
|
|
65
|
-
<a id="namespace"></a>• [`namespace`](#namespace) - Optional String<br>Namespace for the Child Tenant. For this resource type, namespace should be empty or omitted
|
|
66
|
-
|
|
67
67
|
### Spec Argument Reference
|
|
68
68
|
|
|
69
69
|
<a id="child-tenant-manager"></a>• [`child_tenant_manager`](#child-tenant-manager) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Child Tenant Manager](#child-tenant-manager) below for details.
|
|
@@ -122,43 +122,43 @@ A [`vpc_attachments`](#aws-tgw-site-vpc-attachments) block (within [`aws_tgw_sit
|
|
|
122
122
|
|
|
123
123
|
A [`vpc_list`](#aws-tgw-site-vpc-attachments-vpc-list) block (within [`aws_tgw_site.vpc_attachments`](#aws-tgw-site-vpc-attachments)) supports the following:
|
|
124
124
|
|
|
125
|
-
<a id="
|
|
125
|
+
<a id="routing-287a5f"></a>• [`custom_routing`](#routing-287a5f) - Optional Block<br>AWS Route Table List. AWS Route Table List<br>See [Custom Routing](#routing-287a5f) below.
|
|
126
126
|
|
|
127
|
-
<a id="
|
|
127
|
+
<a id="route-44d7f5"></a>• [`default_route`](#route-44d7f5) - Optional Block<br>Override Default Route Choice. Select Override Default Route Choice<br>See [Default Route](#route-44d7f5) below.
|
|
128
128
|
|
|
129
|
-
<a id="
|
|
129
|
+
<a id="labels-3555f3"></a>• [`labels`](#labels-3555f3) - Optional Block<br>Labels. Add labels for the VPC attachment. These labels can then be used in policies such as enhanced firewall
|
|
130
130
|
|
|
131
|
-
<a id="
|
|
131
|
+
<a id="routing-97ae2a"></a>• [`manual_routing`](#routing-97ae2a) - Optional Block<br>Enable this option
|
|
132
132
|
|
|
133
|
-
<a id="
|
|
133
|
+
<a id="vpc-id-318c59"></a>• [`vpc_id`](#vpc-id-318c59) - Optional String<br>VPC ID. Enter the VPC ID of the VPC to be attached
|
|
134
134
|
|
|
135
135
|
#### AWS TGW Site VPC Attachments VPC List Custom Routing
|
|
136
136
|
|
|
137
|
-
A [`custom_routing`](#
|
|
137
|
+
A [`custom_routing`](#routing-287a5f) block (within [`aws_tgw_site.vpc_attachments.vpc_list`](#aws-tgw-site-vpc-attachments-vpc-list)) supports the following:
|
|
138
138
|
|
|
139
|
-
<a id="
|
|
139
|
+
<a id="tables-ad622a"></a>• [`route_tables`](#tables-ad622a) - Optional Block<br>List of route tables. Route Tables<br>See [Route Tables](#tables-ad622a) below.
|
|
140
140
|
|
|
141
141
|
#### AWS TGW Site VPC Attachments VPC List Custom Routing Route Tables
|
|
142
142
|
|
|
143
|
-
A [`route_tables`](#
|
|
143
|
+
A [`route_tables`](#tables-ad622a) block (within [`aws_tgw_site.vpc_attachments.vpc_list.custom_routing`](#routing-287a5f)) supports the following:
|
|
144
144
|
|
|
145
|
-
<a id="
|
|
145
|
+
<a id="table-id-73e5e3"></a>• [`route_table_id`](#table-id-73e5e3) - Optional String<br>Route table ID. Route table ID
|
|
146
146
|
|
|
147
|
-
<a id="
|
|
147
|
+
<a id="routes-3f9b25"></a>• [`static_routes`](#routes-3f9b25) - Optional List<br>Static Routes. List of Static Routes
|
|
148
148
|
|
|
149
149
|
#### AWS TGW Site VPC Attachments VPC List Default Route
|
|
150
150
|
|
|
151
|
-
A [`default_route`](#
|
|
151
|
+
A [`default_route`](#route-44d7f5) block (within [`aws_tgw_site.vpc_attachments.vpc_list`](#aws-tgw-site-vpc-attachments-vpc-list)) supports the following:
|
|
152
152
|
|
|
153
|
-
<a id="
|
|
153
|
+
<a id="tables-cc89f6"></a>• [`all_route_tables`](#tables-cc89f6) - Optional Block<br>Enable this option
|
|
154
154
|
|
|
155
|
-
<a id="
|
|
155
|
+
<a id="tables-6ffd1a"></a>• [`selective_route_tables`](#tables-6ffd1a) - Optional Block<br>AWS Route Table. AWS Route Table<br>See [Selective Route Tables](#tables-6ffd1a) below.
|
|
156
156
|
|
|
157
157
|
#### AWS TGW Site VPC Attachments VPC List Default Route Selective Route Tables
|
|
158
158
|
|
|
159
|
-
A [`selective_route_tables`](#
|
|
159
|
+
A [`selective_route_tables`](#tables-6ffd1a) block (within [`aws_tgw_site.vpc_attachments.vpc_list.default_route`](#route-44d7f5)) supports the following:
|
|
160
160
|
|
|
161
|
-
<a id="
|
|
161
|
+
<a id="table-id-4ea496"></a>• [`route_table_id`](#table-id-4ea496) - Optional List<br>Route table ID. Route table ID
|
|
162
162
|
|
|
163
163
|
#### Azure VNET Site
|
|
164
164
|
|
|
@@ -182,51 +182,51 @@ A [`site`](#azure-vnet-site-site) block (within [`azure_vnet_site`](#azure-vnet-
|
|
|
182
182
|
|
|
183
183
|
A [`vnet_attachments`](#azure-vnet-site-vnet-attachments) block (within [`azure_vnet_site`](#azure-vnet-site)) supports the following:
|
|
184
184
|
|
|
185
|
-
<a id="
|
|
185
|
+
<a id="list-5826e3"></a>• [`vnet_list`](#list-5826e3) - Optional Block<br>VNET List<br>See [VNET List](#list-5826e3) below.
|
|
186
186
|
|
|
187
187
|
#### Azure VNET Site VNET Attachments VNET List
|
|
188
188
|
|
|
189
|
-
A [`vnet_list`](#
|
|
189
|
+
A [`vnet_list`](#list-5826e3) block (within [`azure_vnet_site.vnet_attachments`](#azure-vnet-site-vnet-attachments)) supports the following:
|
|
190
190
|
|
|
191
|
-
<a id="
|
|
191
|
+
<a id="routing-724341"></a>• [`custom_routing`](#routing-724341) - Optional Block<br>List Azure Route Table with Static Route. List Azure Route Table with Static Route<br>See [Custom Routing](#routing-724341) below.
|
|
192
192
|
|
|
193
|
-
<a id="
|
|
193
|
+
<a id="route-fd5eea"></a>• [`default_route`](#route-fd5eea) - Optional Block<br>Override Default Route Choice. Select Override Default Route Choice<br>See [Default Route](#route-fd5eea) below.
|
|
194
194
|
|
|
195
|
-
<a id="
|
|
195
|
+
<a id="labels-e777f2"></a>• [`labels`](#labels-e777f2) - Optional Block<br>Labels. Add labels for the VNET attachments. These labels can then be used in policies such as enhanced firewall policies
|
|
196
196
|
|
|
197
|
-
<a id="
|
|
197
|
+
<a id="routing-e423fa"></a>• [`manual_routing`](#routing-e423fa) - Optional Block<br>Enable this option
|
|
198
198
|
|
|
199
|
-
<a id="
|
|
199
|
+
<a id="subscription-id-9a0b4f"></a>• [`subscription_id`](#subscription-id-9a0b4f) - Optional String<br>Subscription ID. Enter the Subscription ID of the VNET to be attached
|
|
200
200
|
|
|
201
|
-
<a id="
|
|
201
|
+
<a id="vnet-id-6eb10e"></a>• [`vnet_id`](#vnet-id-6eb10e) - Optional String<br>VNET ID. Enter the VNET ID of the VNET to be attached in format /`<resource-group-name>`/`<VNET-name>`
|
|
202
202
|
|
|
203
203
|
#### Azure VNET Site VNET Attachments VNET List Custom Routing
|
|
204
204
|
|
|
205
|
-
A [`custom_routing`](#
|
|
205
|
+
A [`custom_routing`](#routing-724341) block (within [`azure_vnet_site.vnet_attachments.vnet_list`](#list-5826e3)) supports the following:
|
|
206
206
|
|
|
207
|
-
<a id="
|
|
207
|
+
<a id="tables-722439"></a>• [`route_tables`](#tables-722439) - Optional Block<br>List of route tables with static routes. Route Tables with static routes<br>See [Route Tables](#tables-722439) below.
|
|
208
208
|
|
|
209
209
|
#### Azure VNET Site VNET Attachments VNET List Custom Routing Route Tables
|
|
210
210
|
|
|
211
|
-
A [`route_tables`](#
|
|
211
|
+
A [`route_tables`](#tables-722439) block (within [`azure_vnet_site.vnet_attachments.vnet_list.custom_routing`](#routing-724341)) supports the following:
|
|
212
212
|
|
|
213
|
-
<a id="
|
|
213
|
+
<a id="table-id-64761a"></a>• [`route_table_id`](#table-id-64761a) - Optional String<br>Route table ID. Route table ID in the format /`<resource-group-name>`/`<route-table-name>`
|
|
214
214
|
|
|
215
|
-
<a id="
|
|
215
|
+
<a id="routes-18e053"></a>• [`static_routes`](#routes-18e053) - Optional List<br>Static Routes. List of Static Routes
|
|
216
216
|
|
|
217
217
|
#### Azure VNET Site VNET Attachments VNET List Default Route
|
|
218
218
|
|
|
219
|
-
A [`default_route`](#
|
|
219
|
+
A [`default_route`](#route-fd5eea) block (within [`azure_vnet_site.vnet_attachments.vnet_list`](#list-5826e3)) supports the following:
|
|
220
220
|
|
|
221
|
-
<a id="
|
|
221
|
+
<a id="tables-19f37b"></a>• [`all_route_tables`](#tables-19f37b) - Optional Block<br>Enable this option
|
|
222
222
|
|
|
223
|
-
<a id="
|
|
223
|
+
<a id="tables-97cee7"></a>• [`selective_route_tables`](#tables-97cee7) - Optional Block<br>Azure Route Table. Azure Route Table<br>See [Selective Route Tables](#tables-97cee7) below.
|
|
224
224
|
|
|
225
225
|
#### Azure VNET Site VNET Attachments VNET List Default Route Selective Route Tables
|
|
226
226
|
|
|
227
|
-
A [`selective_route_tables`](#
|
|
227
|
+
A [`selective_route_tables`](#tables-97cee7) block (within [`azure_vnet_site.vnet_attachments.vnet_list.default_route`](#route-fd5eea)) supports the following:
|
|
228
228
|
|
|
229
|
-
<a id="
|
|
229
|
+
<a id="table-id-062f6e"></a>• [`route_table_id`](#table-id-062f6e) - Optional List<br>Route table ID. Route table ID in the format /`<resource-group-name>`/`<route-table-name>`
|
|
230
230
|
|
|
231
231
|
#### Segment
|
|
232
232
|
|
|
@@ -90,7 +90,7 @@ An [`aws_assume_role`](#aws-assume-role) block supports the following:
|
|
|
90
90
|
|
|
91
91
|
<a id="aws-assume-role-external-id-is-optional"></a>• [`external_id_is_optional`](#aws-assume-role-external-id-is-optional) - Optional Block<br>Enable this option
|
|
92
92
|
|
|
93
|
-
<a id="
|
|
93
|
+
<a id="tenant-id-b8874c"></a>• [`external_id_is_tenant_id`](#tenant-id-b8874c) - Optional Block<br>Enable this option
|
|
94
94
|
|
|
95
95
|
<a id="aws-assume-role-role-arn"></a>• [`role_arn`](#aws-assume-role-role-arn) - Optional String<br>IAM Role ARN. IAM Role ARN to assume the role
|
|
96
96
|
|
|
@@ -110,27 +110,27 @@ An [`aws_secret_key`](#aws-secret-key) block supports the following:
|
|
|
110
110
|
|
|
111
111
|
A [`secret_key`](#aws-secret-key-secret-key) block (within [`aws_secret_key`](#aws-secret-key)) supports the following:
|
|
112
112
|
|
|
113
|
-
<a id="
|
|
113
|
+
<a id="info-9190c7"></a>• [`blindfold_secret_info`](#info-9190c7) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-9190c7) below.
|
|
114
114
|
|
|
115
|
-
<a id="
|
|
115
|
+
<a id="info-498ec7"></a>• [`clear_secret_info`](#info-498ec7) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-498ec7) below.
|
|
116
116
|
|
|
117
117
|
#### AWS Secret Key Secret Key Blindfold Secret Info
|
|
118
118
|
|
|
119
|
-
A [`blindfold_secret_info`](#
|
|
119
|
+
A [`blindfold_secret_info`](#info-9190c7) block (within [`aws_secret_key.secret_key`](#aws-secret-key-secret-key)) supports the following:
|
|
120
120
|
|
|
121
|
-
<a id="
|
|
121
|
+
<a id="provider-d58e76"></a>• [`decryption_provider`](#provider-d58e76) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
|
|
122
122
|
|
|
123
|
-
<a id="
|
|
123
|
+
<a id="location-b28fee"></a>• [`location`](#location-b28fee) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
|
|
124
124
|
|
|
125
|
-
<a id="
|
|
125
|
+
<a id="provider-984153"></a>• [`store_provider`](#provider-984153) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
126
126
|
|
|
127
127
|
#### AWS Secret Key Secret Key Clear Secret Info
|
|
128
128
|
|
|
129
|
-
A [`clear_secret_info`](#
|
|
129
|
+
A [`clear_secret_info`](#info-498ec7) block (within [`aws_secret_key.secret_key`](#aws-secret-key-secret-key)) supports the following:
|
|
130
130
|
|
|
131
|
-
<a id="
|
|
131
|
+
<a id="ref-647211"></a>• [`provider_ref`](#ref-647211) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
132
132
|
|
|
133
|
-
<a id="
|
|
133
|
+
<a id="url-7236fa"></a>• [`url`](#url-7236fa) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
|
|
134
134
|
|
|
135
135
|
#### Azure Client Secret
|
|
136
136
|
|
|
@@ -148,27 +148,27 @@ An [`azure_client_secret`](#azure-client-secret) block supports the following:
|
|
|
148
148
|
|
|
149
149
|
A [`client_secret`](#azure-client-secret-client-secret) block (within [`azure_client_secret`](#azure-client-secret)) supports the following:
|
|
150
150
|
|
|
151
|
-
<a id="
|
|
151
|
+
<a id="info-2956b6"></a>• [`blindfold_secret_info`](#info-2956b6) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-2956b6) below.
|
|
152
152
|
|
|
153
|
-
<a id="
|
|
153
|
+
<a id="info-3d8384"></a>• [`clear_secret_info`](#info-3d8384) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-3d8384) below.
|
|
154
154
|
|
|
155
155
|
#### Azure Client Secret Client Secret Blindfold Secret Info
|
|
156
156
|
|
|
157
|
-
A [`blindfold_secret_info`](#
|
|
157
|
+
A [`blindfold_secret_info`](#info-2956b6) block (within [`azure_client_secret.client_secret`](#azure-client-secret-client-secret)) supports the following:
|
|
158
158
|
|
|
159
|
-
<a id="
|
|
159
|
+
<a id="provider-1823dc"></a>• [`decryption_provider`](#provider-1823dc) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
|
|
160
160
|
|
|
161
|
-
<a id="
|
|
161
|
+
<a id="location-7d1410"></a>• [`location`](#location-7d1410) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
|
|
162
162
|
|
|
163
|
-
<a id="
|
|
163
|
+
<a id="provider-5a31e4"></a>• [`store_provider`](#provider-5a31e4) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
164
164
|
|
|
165
165
|
#### Azure Client Secret Client Secret Clear Secret Info
|
|
166
166
|
|
|
167
|
-
A [`clear_secret_info`](#
|
|
167
|
+
A [`clear_secret_info`](#info-3d8384) block (within [`azure_client_secret.client_secret`](#azure-client-secret-client-secret)) supports the following:
|
|
168
168
|
|
|
169
|
-
<a id="
|
|
169
|
+
<a id="ref-5a50b3"></a>• [`provider_ref`](#ref-5a50b3) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
170
170
|
|
|
171
|
-
<a id="
|
|
171
|
+
<a id="url-50a78b"></a>• [`url`](#url-50a78b) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
|
|
172
172
|
|
|
173
173
|
#### Azure Pfx Certificate
|
|
174
174
|
|
|
@@ -188,27 +188,27 @@ An [`azure_pfx_certificate`](#azure-pfx-certificate) block supports the followin
|
|
|
188
188
|
|
|
189
189
|
A [`password`](#azure-pfx-certificate-password) block (within [`azure_pfx_certificate`](#azure-pfx-certificate)) supports the following:
|
|
190
190
|
|
|
191
|
-
<a id="
|
|
191
|
+
<a id="info-86ae9f"></a>• [`blindfold_secret_info`](#info-86ae9f) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-86ae9f) below.
|
|
192
192
|
|
|
193
|
-
<a id="
|
|
193
|
+
<a id="info-b6797c"></a>• [`clear_secret_info`](#info-b6797c) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-b6797c) below.
|
|
194
194
|
|
|
195
195
|
#### Azure Pfx Certificate Password Blindfold Secret Info
|
|
196
196
|
|
|
197
|
-
A [`blindfold_secret_info`](#
|
|
197
|
+
A [`blindfold_secret_info`](#info-86ae9f) block (within [`azure_pfx_certificate.password`](#azure-pfx-certificate-password)) supports the following:
|
|
198
198
|
|
|
199
|
-
<a id="
|
|
199
|
+
<a id="provider-669799"></a>• [`decryption_provider`](#provider-669799) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
|
|
200
200
|
|
|
201
|
-
<a id="
|
|
201
|
+
<a id="location-24612c"></a>• [`location`](#location-24612c) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
|
|
202
202
|
|
|
203
|
-
<a id="
|
|
203
|
+
<a id="provider-65421b"></a>• [`store_provider`](#provider-65421b) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
204
204
|
|
|
205
205
|
#### Azure Pfx Certificate Password Clear Secret Info
|
|
206
206
|
|
|
207
|
-
A [`clear_secret_info`](#
|
|
207
|
+
A [`clear_secret_info`](#info-b6797c) block (within [`azure_pfx_certificate.password`](#azure-pfx-certificate-password)) supports the following:
|
|
208
208
|
|
|
209
|
-
<a id="
|
|
209
|
+
<a id="ref-9cabcd"></a>• [`provider_ref`](#ref-9cabcd) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
210
210
|
|
|
211
|
-
<a id="
|
|
211
|
+
<a id="url-fdff02"></a>• [`url`](#url-fdff02) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
|
|
212
212
|
|
|
213
213
|
#### GCP Cred File
|
|
214
214
|
|
|
@@ -220,27 +220,27 @@ A [`gcp_cred_file`](#gcp-cred-file) block supports the following:
|
|
|
220
220
|
|
|
221
221
|
A [`credential_file`](#gcp-cred-file-credential-file) block (within [`gcp_cred_file`](#gcp-cred-file)) supports the following:
|
|
222
222
|
|
|
223
|
-
<a id="
|
|
223
|
+
<a id="info-3869e4"></a>• [`blindfold_secret_info`](#info-3869e4) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-3869e4) below.
|
|
224
224
|
|
|
225
|
-
<a id="
|
|
225
|
+
<a id="info-226bef"></a>• [`clear_secret_info`](#info-226bef) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-226bef) below.
|
|
226
226
|
|
|
227
227
|
#### GCP Cred File Credential File Blindfold Secret Info
|
|
228
228
|
|
|
229
|
-
A [`blindfold_secret_info`](#
|
|
229
|
+
A [`blindfold_secret_info`](#info-3869e4) block (within [`gcp_cred_file.credential_file`](#gcp-cred-file-credential-file)) supports the following:
|
|
230
230
|
|
|
231
|
-
<a id="
|
|
231
|
+
<a id="provider-492d2f"></a>• [`decryption_provider`](#provider-492d2f) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
|
|
232
232
|
|
|
233
|
-
<a id="
|
|
233
|
+
<a id="location-4d37cb"></a>• [`location`](#location-4d37cb) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
|
|
234
234
|
|
|
235
|
-
<a id="
|
|
235
|
+
<a id="provider-f34db4"></a>• [`store_provider`](#provider-f34db4) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
236
236
|
|
|
237
237
|
#### GCP Cred File Credential File Clear Secret Info
|
|
238
238
|
|
|
239
|
-
A [`clear_secret_info`](#
|
|
239
|
+
A [`clear_secret_info`](#info-226bef) block (within [`gcp_cred_file.credential_file`](#gcp-cred-file-credential-file)) supports the following:
|
|
240
240
|
|
|
241
|
-
<a id="
|
|
241
|
+
<a id="ref-4b930a"></a>• [`provider_ref`](#ref-4b930a) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
242
242
|
|
|
243
|
-
<a id="
|
|
243
|
+
<a id="url-7669b2"></a>• [`url`](#url-7669b2) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
|
|
244
244
|
|
|
245
245
|
#### Timeouts
|
|
246
246
|
|
|
@@ -126,13 +126,13 @@ A [`connections`](#aws-byoc-connections) block (within [`aws.byoc`](#aws-byoc))
|
|
|
126
126
|
|
|
127
127
|
<a id="aws-byoc-connections-region"></a>• [`region`](#aws-byoc-connections-region) - Optional String<br>Region. Region where the connection is setup
|
|
128
128
|
|
|
129
|
-
<a id="
|
|
129
|
+
<a id="name-ebc6a3"></a>• [`system_generated_name`](#name-ebc6a3) - Optional Block<br>Enable this option
|
|
130
130
|
|
|
131
131
|
<a id="aws-byoc-connections-tags"></a>• [`tags`](#aws-byoc-connections-tags) - Optional Block<br>AWS Tags. AWS Tags is a label consisting of a user-defined key and value. It helps to manage, identify, organize, search for, and filter resources in AWS console. Specified tags will be added to Virtual interface along with any F5XC specific tags
|
|
132
132
|
|
|
133
133
|
<a id="aws-byoc-connections-user-assigned-name"></a>• [`user_assigned_name`](#aws-byoc-connections-user-assigned-name) - Optional String<br>User Assigned. User is managing the AWS resource name
|
|
134
134
|
|
|
135
|
-
<a id="
|
|
135
|
+
<a id="type-228d5c"></a>• [`virtual_interface_type`](#type-228d5c) - Optional String Defaults to `PRIVATE`<br>[Enum: PRIVATE] Virtual Interface Type. Defines the type of virtual interface that needs to be configured on AWS - PRIVATE: Private A private virtual interface should be used to access an Amazon VPC using private IP addresses. - TRANSIT: Transit A transit virtual interface is a VLAN that transports traffic from a Direct Connect gateway to one or more transit gateways. The only possible value is `PRIVATE`
|
|
136
136
|
|
|
137
137
|
<a id="aws-byoc-connections-vlan"></a>• [`vlan`](#aws-byoc-connections-vlan) - Optional Number<br>Virtual Local Area Network (VLAN). Virtual Local Area Network number for the new virtual interface to be configured on the AWS. This tag is required for any traffic traversing the AWS Direct Connect connection
|
|
138
138
|
|
|
@@ -140,41 +140,41 @@ A [`connections`](#aws-byoc-connections) block (within [`aws.byoc`](#aws-byoc))
|
|
|
140
140
|
|
|
141
141
|
An [`auth_key`](#aws-byoc-connections-auth-key) block (within [`aws.byoc.connections`](#aws-byoc-connections)) supports the following:
|
|
142
142
|
|
|
143
|
-
<a id="
|
|
143
|
+
<a id="info-79ff82"></a>• [`blindfold_secret_info`](#info-79ff82) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-79ff82) below.
|
|
144
144
|
|
|
145
|
-
<a id="
|
|
145
|
+
<a id="info-dc68b3"></a>• [`clear_secret_info`](#info-dc68b3) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-dc68b3) below.
|
|
146
146
|
|
|
147
147
|
#### AWS Byoc Connections Auth Key Blindfold Secret Info
|
|
148
148
|
|
|
149
|
-
A [`blindfold_secret_info`](#
|
|
149
|
+
A [`blindfold_secret_info`](#info-79ff82) block (within [`aws.byoc.connections.auth_key`](#aws-byoc-connections-auth-key)) supports the following:
|
|
150
150
|
|
|
151
|
-
<a id="
|
|
151
|
+
<a id="provider-d0a324"></a>• [`decryption_provider`](#provider-d0a324) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
|
|
152
152
|
|
|
153
|
-
<a id="
|
|
153
|
+
<a id="location-2c236d"></a>• [`location`](#location-2c236d) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
|
|
154
154
|
|
|
155
|
-
<a id="
|
|
155
|
+
<a id="provider-01aee0"></a>• [`store_provider`](#provider-01aee0) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
156
156
|
|
|
157
157
|
#### AWS Byoc Connections Auth Key Clear Secret Info
|
|
158
158
|
|
|
159
|
-
A [`clear_secret_info`](#
|
|
159
|
+
A [`clear_secret_info`](#info-dc68b3) block (within [`aws.byoc.connections.auth_key`](#aws-byoc-connections-auth-key)) supports the following:
|
|
160
160
|
|
|
161
|
-
<a id="
|
|
161
|
+
<a id="ref-3bbbbe"></a>• [`provider_ref`](#ref-3bbbbe) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
|
|
162
162
|
|
|
163
|
-
<a id="
|
|
163
|
+
<a id="url-492082"></a>• [`url`](#url-492082) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
|
|
164
164
|
|
|
165
165
|
#### AWS Byoc Connections IPv4
|
|
166
166
|
|
|
167
167
|
An [`ipv4`](#aws-byoc-connections-ipv4) block (within [`aws.byoc.connections`](#aws-byoc-connections)) supports the following:
|
|
168
168
|
|
|
169
|
-
<a id="
|
|
169
|
+
<a id="address-e6b5fb"></a>• [`aws_router_peer_address`](#address-e6b5fb) - Optional String<br>AWS Router IP/Prefix. The BGP peer IP configured on the AWS endpoint
|
|
170
170
|
|
|
171
|
-
<a id="
|
|
171
|
+
<a id="address-f93baf"></a>• [`router_peer_address`](#address-f93baf) - Optional String<br>Customer Router IP/Prefix. The BGP peer IP configured on your (customer) endpoint
|
|
172
172
|
|
|
173
173
|
#### AWS Byoc Connections Metadata
|
|
174
174
|
|
|
175
175
|
A [`metadata`](#aws-byoc-connections-metadata) block (within [`aws.byoc.connections`](#aws-byoc-connections)) supports the following:
|
|
176
176
|
|
|
177
|
-
<a id="
|
|
177
|
+
<a id="spec-644d4f"></a>• [`description_spec`](#spec-644d4f) - Optional String<br>Description. Human readable description
|
|
178
178
|
|
|
179
179
|
<a id="aws-byoc-connections-metadata-name"></a>• [`name`](#aws-byoc-connections-metadata-name) - Optional String<br>Name. This is the name of the message. The value of name has to follow DNS-1035 format
|
|
180
180
|
|
|
@@ -202,7 +202,7 @@ A [`byoc`](#gcp-byoc) block (within [`gcp`](#gcp)) supports the following:
|
|
|
202
202
|
|
|
203
203
|
A [`connections`](#gcp-byoc-connections) block (within [`gcp.byoc`](#gcp-byoc)) supports the following:
|
|
204
204
|
|
|
205
|
-
<a id="
|
|
205
|
+
<a id="name-35ddb5"></a>• [`interconnect_attachment_name`](#name-35ddb5) - Optional String<br>Interconnect Attachment Name. Name of already-existing GCP Cloud Interconnect Attachment
|
|
206
206
|
|
|
207
207
|
<a id="gcp-byoc-connections-metadata"></a>• [`metadata`](#gcp-byoc-connections-metadata) - Optional Block<br>Message Metadata. 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 and replace APIs<br>See [Metadata](#gcp-byoc-connections-metadata) below.
|
|
208
208
|
|
|
@@ -216,7 +216,7 @@ A [`connections`](#gcp-byoc-connections) block (within [`gcp.byoc`](#gcp-byoc))
|
|
|
216
216
|
|
|
217
217
|
A [`metadata`](#gcp-byoc-connections-metadata) block (within [`gcp.byoc.connections`](#gcp-byoc-connections)) supports the following:
|
|
218
218
|
|
|
219
|
-
<a id="
|
|
219
|
+
<a id="spec-5e10f2"></a>• [`description_spec`](#spec-5e10f2) - Optional String<br>Description. Human readable description
|
|
220
220
|
|
|
221
221
|
<a id="gcp-byoc-connections-metadata-name"></a>• [`name`](#gcp-byoc-connections-metadata-name) - Optional String<br>Name. This is the name of the message. The value of name has to follow DNS-1035 format
|
|
222
222
|
|