An App Platform Whose Components Are Actually Deployed

A CAE environment, application and components. deploy_after_create is off in the API, so a component exists with a source, a runtime and a replica count and serves nothing; it is on here. The runtime list still offers Java8, Nodejs8 and Php7, which the module names and asks about, and 500m of CPU cannot take 4Gi of memory.

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 CloudServerless & Containersv1.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 FunctionGraph Function with Its Own Agency, LTS Logs, and Secrets Encrypted with Your Key A Static Site Where Encrypting the Bucket Would Break It

The same job on other clouds

Managed App Platform 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 Service where a Push Is Not a DeployAWS Azure App Service (Linux Web App)Azure DigitalOcean App Platform ServiceDigitalOcean The App Engine Application: One per Project, ForeverGoogle Cloud

Installing it

module "huawei_app_platform" {
  source  = "www.iac-bazaar.com/iac-bazaar/huawei-app-platform/huaweicloud"
  version = "1.0.0"
}

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