A Huawei Cloud VPC with Zonal Subnets, DNS You Chose, and a Range Checked Private
A Huawei Cloud VPC whose range is checked against RFC 1918 (a public range by name), with subnets placed in the zones you name, each with its gateway at the first address and DHCP handing out Huawei's resolvers so the platform's service names resolve. Nothing egresses: a NAT gateway (huawei-nat-gateway) or an EIP is a separate decision.
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.
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.
The same job on other clouds
Virtual Private Cloud (VPC) 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.
Installing it
module "huawei_vpc" {
source = "www.iac-bazaar.com/iac-bazaar/huawei-vpc/huaweicloud"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.