A Bastion That Carves a Range Out of Your VPC and Caps What You Can Register
A Tencent Bastion Host deployment. cidr_block is a range the service claims inside your VPC and an overlap is found by whatever stops working, not by the plan. resource_node is both the bill and the ceiling: registering more assets than you bought fails at registration, months later. time_unit is months and nothing else.
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
Private Instance Access 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 "tencent_bastion" {
source = "www.iac-bazaar.com/iac-bazaar/tencent-bastion/tencentcloud"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.