A Container Registry Namespace with the Retention Policy that Keeps It from Filling

An IBM Cloud Container Registry namespace in the provider's region, with a retention policy that keeps the last ten images per repository and drops untagged ones, because without one every CI run adds an image until the account's storage quota refuses the next push. Quotas and the plan are account-wide and not managed here.

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.

terraformIBM CloudContainer Registryv1.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

Nothing else in the catalogue covers container registry on IBM Cloud. If this module is not the right shape, the closest options are on other clouds.

The same job on other clouds

Container Registry 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 Container Registry Whose Credentials ExpireDigitalOcean A Private Registry Namespace with a Push Key that Is Scoped and ExpiresScaleway A Private Registry that Answers Only to the Ranges You SayOVHcloud A Private Vultr Container Registry on the Plan You ChoseVultr A TCR Basic Instance, Private, with Namespaces that Scan on Push and Refuse Vulnerable ImagesTencent Cloud An SWR Organization with Private RepositoriesHuawei Cloud Artifact Registry RepositoriesGoogle Cloud Azure Container RegistryAzure ECR RepositoryAWS Repositories that Are Declared, Private and ImmutableOracle Cloud

Installing it

module "ibm_container_registry" {
  source  = "www.iac-bazaar.com/iac-bazaar/ibm-container-registry/ibmcloud"
  version = "1.0.0"
}

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