A VPC Peering with the Routes on Both Sides and the Cross-Tenant Case Refused Early

A peering connection between two VPCs with a route written into every route table you list, on both sides, for every CIDR of the other side. A cross-tenant peering sits in PENDING_ACCEPTANCE and its other side is out of reach of this provider, so the module refuses an accepter route table list in that case rather than failing at apply.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformHuawei CloudNetworking & VPCv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Huawei Cloud VPC with Zonal Subnets, DNS You Chose, and a Range Checked Private A Public NAT Gateway for an Existing VPC with Its EIP and SNAT Rules A VPC Endpoint Whitelisted to the CIDRs You Name, with Private DNS A Virtual Gateway and Interface with the BGP Session Authenticated and BFD On An Active-Active VPN Gateway with a Connection from Each Public IP on IKEv2 with Pinned Cryptography An Enterprise Router across Two Zones with Explicit Route Tables and a VPC Attachment per VPC

The same job on other clouds

Network Peering on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

A Cross-Region DRG Peering that Says What It Still NeedsOracle Cloud A Local Peering Gateway Pair that Is Connected and RoutedOracle Cloud A Peering Connection with the Route Table Entries on Both Sides, Postpaid by DefaultTencent Cloud A VPC Peer Connection with the Route Entries on Both Sides That Make It Carry TrafficAlibaba Cloud A VPC Peering Accepted in One Apply, with DNS Across It and Routes on Both SidesAWS Both Halves of a Hub-and-Spoke VNet Peering with Gateway Transit Set as a PairAzure The One Peering Where the Routes Are Programmed for You, and What That Costs You InsteadDigitalOcean VPC Peering in Both Directions with the Routes StatedGoogle Cloud

Installing it

module "huawei_vpc_peering" {
  source  = "www.iac-bazaar.com/iac-bazaar/huawei-vpc-peering/huaweicloud"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.