Akamai CLI, Checked Against The Hash Akamai Calls A Signature

akamai on EL 10 from the GitHub release, refused by Ansible's get_url unless its SHA-256 is the one pinned beside the version: the value Akamai publishes as a .sig file, which is not a signature but the bare hash of the binary. The live test checksums the asset again and runs the CLI to its command list. Sub-CLIs and credentials are per user. 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.

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 ci/cd & automation on Akamai. If this module is not the right shape, the closest options are on other clouds.

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_akamai_cli" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-akamai-cli/akamai"
  version = "1.0.0"
}

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