Scaleway CLI, Checked And Quiet

scaleway-cli

The Scaleway CLI (scw) on EL 10 from the vendor's GitHub release, checked against the SHA-256 the vendor published beside it, pinned to a version, installed as root's binary in /usr/local/bin. Original role for EL 10, live-tested with podman on Rocky Linux 10.

No package, so the checksum is the whole story. EL 10 carries no scw; Scaleway ships versioned releases on GitHub with a checksum file (SHA256SUMS) beside the assets. Most installs curl the asset and never open that file. This role downloads both and has Ansible's get_url refuse the asset unless its SHA-256 is the one in the vendor's file; the live test runs sha256sum -c against the same file afterwards. A download is verified against what Scaleway published, not against what happened to arrive.

Pinned. scaleway_cli_version is what gets installed, kept in a directory of its own (/usr/local/src/scw-<version>) so the checksum file and the asset it names stay together. A newer release is a variable change and a run; the same version is changed=0.

Proven to run. The live test calls scw account project list with no credentials and expects the CLI to get to "No credentials provided" - the binary, its Scaleway client and its configuration lookup all ran; only the credentials were missing.

The asset is the binary, and telemetry is on by default. Scaleway ships the CLI as a bare executable (no archive) with SHA256SUMS beside it, and the CLI sends usage telemetry unless send-telemetry is off. The role exports SCW_SEND_TELEMETRY=false from /etc/profile.d for every user, and the live test reads it back.

License

Commercial - IaC Bazaar EULA. (c) IaC Bazaar.