yq, Pinned From A Checksum File get_url Cannot Read

Mike Farah's yq on EL 10 from the GitHub release, refused by get_url unless its SHA-256 is the pinned one: yq's checksum files are rhash and BSD forms that get_url cannot parse, so the live test fetches checksums-bsd for the version and asserts the SHA256 line is the pin, then reads a key from a YAML file through yq. 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.

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 Infracost, Checked, And Not Checking For Updates Nomad CLI, SHA256SUMS Signed By HashiCorp OPA, A Real Policy Evaluated OpenTofu, SHA256SUMS Signed By OpenTofu's Key

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_yq" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-yq/any"
  version = "1.0.0"
}

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