Exoscale CLI, Checked, With Its Own Completion

exoscale-cli

The Exoscale CLI (exo) 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 exo; Exoscale ships versioned releases on GitHub with a checksum file (exoscale-cli_1.100.0_checksums.txt) 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 Exoscale published, not against what happened to arrive.

Pinned. exoscale_cli_version is what gets installed, kept in a directory of its own (/usr/local/src/exo-<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 exo compute instance list with no credentials and expects the CLI to get to "must be configured before usage" - the binary, its Exoscale client and its configuration lookup all ran; only the credentials were missing.

Completion from the release itself. The tarball carries contrib/completion/bash/exo; the role installs it under /etc/bash_completion.d so it matches the installed version exactly. Exoscale also publishes .sig files (and an rpm); this role verifies the SHA-256, not those signatures.

License

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