A Backup Vault with Enforced Retention and Resources that Follow It
The vault and the plan are what the console shows; the association is what makes a backup exist, and a plan associated with nothing backs up nothing. Enforced retention is the setting ransomware cannot undo - no backup younger than it can be deleted by anyone - and WITHIN_PROJECT access lets a compromised owner restore everything. Resources come with the plan; 14 days enforced; org-scoped.
This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to download 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
Backup Service 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 "gcp_backup_dr" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-backup-dr/gcp"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.