You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: fixed bug which was causing the error 'CreateVPCDnsResolutionBindingWithContext failed: This VPC already contains DNS Resolution Bindings' (#1010)
### Upgrade notice for Hub-and-Spoke topology users (version 8.0.0 and above)
24
+
25
+
> **Note:** This upgrade notice applies **only** to users of the advanced Hub-and-Spoke VPC topology who are upgrading from a previous version of this module to v8.0.0 or later. If you are using the standard topology, or a new user starting with v8.0.0 or above, you can safely ignore this section.
26
+
27
+
If you are upgrading, note that the `ibm_is_vpc_dns_resolution_binding` resources are no longer used for DNS resolution binding with the `Delegated` resolver type.
28
+
29
+
- Upgrade to the latest module (>= `v8.0.0`).
30
+
- Set `update_delegated_resolver = true` in your Terraform configuration (along with any other input parameters you previously used) and run `terraform apply` to re-create the DNS resolution binding with the `Delegated` resolver type. For example:
Expected network connectivity downtime of typically around 20 seconds.
37
+
21
38
<!-- Below content is automatically populated via pre-commit hook -->
22
39
<!-- BEGIN OVERVIEW HOOK -->
23
40
## Overview
@@ -177,6 +194,7 @@ To attach access management tags to resources in this module, you need the follo
177
194
|[ibm_is_subnet.subnet](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_subnet)| data source |
178
195
|[ibm_is_vpc.vpc](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_vpc)| data source |
179
196
|[ibm_is_vpc_address_prefixes.get_address_prefixes](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_vpc_address_prefixes)| data source |
197
+
|[ibm_is_vpc_dns_resolution_bindings.dns_bindings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_vpc_dns_resolution_bindings)| data source |
180
198
181
199
### Inputs
182
200
@@ -220,7 +238,7 @@ To attach access management tags to resources in this module, you need the follo
220
238
| <aname="input_prefix"></a> [prefix](#input\_prefix)| The value that you would like to prefix to the name of the resources provisioned by this module. Explicitly set to null if you do not wish to use a prefix. This value is ignored if using one of the optional variables for explicit control over naming. |`string`|`null`| no |
221
239
| <aname="input_public_gateway_name"></a> [public\_gateway\_name](#input\_public\_gateway\_name)| The name to give the provisioned VPC public gateways. If not set, the module generates a name based on the `prefix` and `name` variables. |`string`|`null`| no |
222
240
| <aname="input_region"></a> [region](#input\_region)| The region to which to deploy the VPC |`string`| n/a | yes |
223
-
| <aname="input_resolver_type"></a> [resolver\_type](#input\_resolver\_type)| Resolver type. Can be system or manual. For delegated resolver type, see the update\_delegated\_resolver variable instead. |`string`|`null`| no |
241
+
| <aname="input_resolver_type"></a> [resolver\_type](#input\_resolver\_type)| Resolver type. Can be system or manual or delegated. |`string`|`null`| no |
224
242
| <aname="input_resource_group_id"></a> [resource\_group\_id](#input\_resource\_group\_id)| The resource group ID where the VPC to be created |`string`| n/a | yes |
225
243
| <aname="input_routes"></a> [routes](#input\_routes)| OPTIONAL - Allows you to specify the next hop for packets based on their destination address | <pre>list(<br/> object({<br/> name = string<br/> route_direct_link_ingress = optional(bool)<br/> route_transit_gateway_ingress = optional(bool)<br/> route_vpc_zone_ingress = optional(bool)<br/> routes = optional(<br/> list(<br/> object({<br/> action = optional(string)<br/> zone = number<br/> destination = string<br/> next_hop = string<br/> })<br/> ))<br/> })<br/> )</pre> |`[]`| no |
226
244
| <aname="input_routing_table_name"></a> [routing\_table\_name](#input\_routing\_table\_name)| The name to give the provisioned routing tables. If not set, the module generates a name based on the `prefix` and `name` variables. |`string`|`null`| no |
@@ -242,8 +260,8 @@ To attach access management tags to resources in this module, you need the follo
242
260
| <aname="output_cidr_blocks"></a> [cidr\_blocks](#output\_cidr\_blocks)| List of CIDR blocks present in VPC stack |
243
261
| <aname="output_custom_resolver_hub"></a> [custom\_resolver\_hub](#output\_custom\_resolver\_hub)| The custom resolver created for the hub vpc. Only set if enable\_hub is set and skip\_custom\_resolver\_hub\_creation is false. |
244
262
| <aname="output_dns_custom_resolver_id"></a> [dns\_custom\_resolver\_id](#output\_dns\_custom\_resolver\_id)| The ID of the DNS Custom Resolver. |
245
-
| <aname="output_dns_endpoint_gateways_by_crn"></a> [dns\_endpoint\_gateways\_by\_crn](#output\_dns\_endpoint\_gateways\_by\_crn)| The list of VPEs that are made available for DNS resolution in the created VPC. Only set if enable\_hub is false and enable\_hub\_vpc\_id are true. |
246
-
| <aname="output_dns_endpoint_gateways_by_id"></a> [dns\_endpoint\_gateways\_by\_id](#output\_dns\_endpoint\_gateways\_by\_id)| The list of VPEs that are made available for DNS resolution in the created VPC. Only set if enable\_hub is false and enable\_hub\_vpc\_id are true. |
263
+
| <aname="output_dns_endpoint_gateways_by_crn"></a> [dns\_endpoint\_gateways\_by\_crn](#output\_dns\_endpoint\_gateways\_by\_crn)| The list of VPEs that are made available for DNS resolution in the created Spoke VPC. Only set if enable\_hub is false and enable\_hub\_vpc\_id OR enable\_hub\_vpc\_crn are true. |
264
+
| <aname="output_dns_endpoint_gateways_by_id"></a> [dns\_endpoint\_gateways\_by\_id](#output\_dns\_endpoint\_gateways\_by\_id)| The list of VPEs that are made available for DNS resolution in the created Spoke VPC. Only set if enable\_hub is false and enable\_hub\_vpc\_id OR enable\_hub\_vpc\_crn are true. |
247
265
| <aname="output_dns_instance_id"></a> [dns\_instance\_id](#output\_dns\_instance\_id)| The ID of the DNS instance. |
248
266
| <aname="output_dns_record_ids"></a> [dns\_record\_ids](#output\_dns\_record\_ids)| List of all the domain resource records. |
249
267
| <aname="output_dns_zone"></a> [dns\_zone](#output\_dns\_zone)| A map representing DNS zone information. |
Copy file name to clipboardExpand all lines: examples/hub-spoke-delegated-resolver/README.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,4 @@ This example demonstrates how to deploy hub and spoke VPCs, inclusive of enablin
12
12
1. The first terraform apply lay down all of the topology, but does not configure the DNS resolver to delegated in the spoke
13
13
2. The second terraform apply should have the update_delegated_resolver variable to true to configure the DNS resolver to be delegated ```terraform apply -var=update_delegated_resolver=true```
14
14
15
-
In order to perform a successful destroy, please set to the resolver to "system" in the spoke VPC through the UI before issuing the terraform destroy - see https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-transit2
16
-
17
15
You may also be interested in the [Hub and Spoke VPC with manual DNS resolver Example](../hub-spoke-manual-resolver/) which does not exhibit those issues.
description="The list of VPEs that are made available for DNS resolution in the created VPC. Only set if enable_hub is false and enable_hub_vpc_id are true."
description="The list of VPEs that are made available for DNS resolution in the created Spoke VPC. Only set if enable_hub is false and enable_hub_vpc_id OR enable_hub_vpc_crn are true."
description="The list of VPEs that are made available for DNS resolution in the created VPC. Only set if enable_hub is false and enable_hub_vpc_id are true."
description="The list of VPEs that are made available for DNS resolution in the created Spoke VPC. Only set if enable_hub is false and enable_hub_vpc_id OR enable_hub_vpc_crn are true."
0 commit comments