feat: surface additional hub-spoke dns sharing outputs (#668)

Author: rajatagarwal-ibm

README.md

@@ -83,8 +83,8 @@ To attach access management tags to resources in this module, you need the follo
 
 - [ Basic Example](examples/basic)
 - [ Default Example](examples/default)
+- [ Hub and Spoke VPC Example](examples/hub-spoke-delegated-resolver)
 - [ Hub and Spoke VPC with manual DNS resolver Example](examples/hub-spoke-manual-resolver)
-- [ Hub and Spoke VPC Example](examples/hub-spoke)
 - [ Landing Zone example](examples/landing_zone)
 - [ No Prefix Example](examples/no-prefix)
 <!-- END EXAMPLES HOOK -->
@@ -176,6 +176,8 @@ To attach access management tags to resources in this module, you need the follo
 |------|-------------|
 | <a name="output_cidr_blocks"></a> [cidr\_blocks](#output\_cidr\_blocks) | List of CIDR blocks present in VPC stack |
 | <a name="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. |
+| <a name="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. |
+| <a name="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. |
 | <a name="output_network_acls"></a> [network\_acls](#output\_network\_acls) | List of shortnames and IDs of network ACLs |
 | <a name="output_public_gateways"></a> [public\_gateways](#output\_public\_gateways) | Map of public gateways by zone |
 | <a name="output_subnet_detail_list"></a> [subnet\_detail\_list](#output\_subnet\_detail\_list) | A list of subnets containing names, CIDR blocks, and zones. |

examples/hub-spoke/README.md …s/hub-spoke-delegated-resolver/README.mdexamples/hub-spoke/README.md renamed to examples/hub-spoke-delegated-resolver/README.md examples/hub-spoke/README.md renamed to examples/hub-spoke-delegated-resolver/README.md

@@ -0,0 +1,53 @@
+##############################################################################
+# Outputs
+##############################################################################
+
+output "hub_vpc_id" {
+  value       = module.hub_vpc.vpc_id
+  description = "Hub VPC id"
+}
+
+output "hub_vpc_crn" {
+  value       = module.hub_vpc.vpc_crn
+  description = "Hub VPC crn"
+}
+
+output "spoke_vpc_id" {
+  value       = module.spoke_vpc.vpc_id
+  description = "Hub VPC id"
+}
+
+output "spoke_vpc_crn" {
+  value       = module.spoke_vpc.vpc_crn
+  description = "Hub VPC crn"
+}
+
+output "transit_gateway_id" {
+  value       = module.tg_gateway_connection.tg_id
+  description = "The ID of the transit gateway"
+}
+
+output "transit_gateway_crn" {
+  value       = module.tg_gateway_connection.tg_crn
+  description = "The CRN of the transit gateway"
+}
+
+output "vpc_connection_ids" {
+  value       = module.tg_gateway_connection.vpc_conn_ids
+  description = "List of VPC connection IDs."
+}
+
+output "custom_resolver_hub_vpc" {
+  value       = module.hub_vpc.custom_resolver_hub
+  description = "The custom resolver created for the hub vpc."
+}
+
+output "dns_endpoint_gateways_by_spoke_vpc_crn" {
+  value       = module.spoke_vpc.dns_endpoint_gateways_by_crn
+  description = "The list of VPEs that are made available for DNS resolution in the created VPC."
+}
+
+output "dns_endpoint_gateways_by_spoke_vpc_id" {
+  value       = module.spoke_vpc.dns_endpoint_gateways_by_id
+  description = "The list of VPEs that are made available for DNS resolution in the created VPC."
+}

examples/hub-spoke/main.tf …les/hub-spoke-delegated-resolver/main.tfexamples/hub-spoke/main.tf renamed to examples/hub-spoke-delegated-resolver/main.tf examples/hub-spoke/main.tf renamed to examples/hub-spoke-delegated-resolver/main.tf

@@ -13,7 +13,7 @@ variable "region" {
 variable "prefix" {
   description = "The prefix that you would like to append to your resources"
   type        = string
-  default     = "hs-vpc"
+  default     = "hs-delegated"
 }
 
 variable "resource_group" {

examples/hub-spoke-delegated-resolver/outputs.tf

@@ -4,4 +4,4 @@ This example demostrates how to deploy hub and spoke VPCs, inclusive of enabling
 
 Caveat: Using a manual resolver, as opposed to a delegated resolver requires to ensure that the custom resolver IPs in the hub VPC do not change outside the terraform lifecycle (which should be the case if you follow a proper IaC approach).
 
-Refer to the documentation [here](../hub-spoke/) if you are new to hub-spoke dns-sharing VPC topology.
+Refer to the documentation [here](../hub-spoke-delegated-resolver/) if you are new to hub-spoke dns-sharing VPC topology.

examples/hub-spoke/provider.tf …hub-spoke-delegated-resolver/provider.tfexamples/hub-spoke/provider.tf renamed to examples/hub-spoke-delegated-resolver/provider.tf examples/hub-spoke/provider.tf renamed to examples/hub-spoke-delegated-resolver/provider.tf

@@ -21,3 +21,33 @@ output "spoke_vpc_crn" {
   value       = module.spoke_vpc.vpc_crn
   description = "Hub VPC crn"
 }
+
+output "transit_gateway_id" {
+  value       = module.tg_gateway_connection.tg_id
+  description = "The ID of the transit gateway"
+}
+
+output "transit_gateway_crn" {
+  value       = module.tg_gateway_connection.tg_crn
+  description = "The CRN of the transit gateway"
+}
+
+output "vpc_connection_ids" {
+  value       = module.tg_gateway_connection.vpc_conn_ids
+  description = "List of VPC connection IDs."
+}
+
+output "custom_resolver_hub_vpc" {
+  value       = module.hub_vpc.custom_resolver_hub
+  description = "The custom resolver created for the hub vpc."
+}
+
+output "dns_endpoint_gateways_by_spoke_vpc_crn" {
+  value       = module.spoke_vpc.dns_endpoint_gateways_by_crn
+  description = "The list of VPEs that are made available for DNS resolution in the created VPC."
+}
+
+output "dns_endpoint_gateways_by_spoke_vpc_id" {
+  value       = module.spoke_vpc.dns_endpoint_gateways_by_id
+  description = "The list of VPEs that are made available for DNS resolution in the created VPC."
+}