A Patch Baseline That Says It Patches Nothing By Itself

An OOS patch baseline: which updates are acceptable on one operating system. A baseline is a policy and an OOS task has to run it, which the module reports rather than letting the word imply a schedule. ALLOW_AS_DEPENDENCY makes a rejection advisory - the patch installs anyway when something approved needs it - so BLOCK is the default.

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.

terraformAlibaba CloudCompute & VMsv1.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.

An ECS Custom Image Captured from an Instance into an Image Family An ECS Instance with a Key Pair, No Public Address, IMDSv2 and an Encrypted Disk

The same job on other clouds

Patch Management 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 Patch Baseline, Its Patch Group and a Maintenance Window that InstallsAWS A Patch Deployment that Targets Hosts and Reboots When NeededGoogle Cloud A Patch Schedule Assigned to Machines that Reboots When NeededAzure A Weekly OS Management Hub Job that Installs Every Update on the Groups You NameOracle Cloud

Installing it

module "alicloud_patch_manager" {
  source  = "www.iac-bazaar.com/iac-bazaar/alicloud-patch-manager/alicloud"
  version = "1.0.0"
}

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