An Organization Whose Policy Types Are Enabled Before a Policy Needs Them

An organization, its units and its accounts. enabled_policy_types is what makes a service control policy attachable at all: without it a policy is created and fails to attach, at apply, behind a clean plan, and neither console connects the two. The account email and phone are the recovery path, so an account with none is listed as an output.

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 CloudLanding Zones & Foundationsv1.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 Service Control Policy Whose Type Decides What Its Document Even Means

The same job on other clouds

Landing Zone 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 Control Tower Landing Zone with Governed Regions, Logging Kept a Year, and Controls per UnitAWS A Resource Directory Where Policy Can Attach and Accounts Can Be DeletedAlibaba Cloud An Organization That Says It Is a Billing Hierarchy, Not a Policy OneTencent Cloud Azure Landing Zone CoreAzure GCP Project FactoryGoogle Cloud

Installing it

module "huawei_landing_zone" {
  source  = "www.iac-bazaar.com/iac-bazaar/huawei-landing-zone/huaweicloud"
  version = "1.0.0"
}

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