tenv, An OpenTofu Installed, Signature-Checked, And Run

tenv on EL 10 from the GitHub release; get_url refuses it unless its SHA-256 is in the vendor's checksums file, and the live test re-checks it, then has tenv tofu install fetch OpenTofu 1.8.7 (the OpenPGP check runs when cosign is absent), lists it and runs it. Shims are opt-in so nothing shadows the host's tofu. Pinned. Original role, live-tested on Rocky Linux 10.

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.

ansibleMulti-cloud & platform-agnosticCI/CD & Automationv1.0.0live-tested

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.

Atmos, A Stack Validated And A Component Described Checkov In A venv Of Its Own Conftest, A Real Policy Evaluated Consul CLI, SHA256SUMS Signed By HashiCorp GitHub CLI, Checked Against The Published Checksums GitLab CLI, Run To GitLab's Door Gitea On Loopback, A Config It Never Writes, A Repository Round-Tripped GoReleaser, A Configuration Validated, A Broken One Refused

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_tenv" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-tenv/any"
  version = "1.0.0"
}

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