Vultr CLI, Checked Against Vultr's Checksums

vultr-cli

The Vultr CLI (vultr-cli) 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 vultr-cli; Vultr ships versioned releases on GitHub with a checksum file (vultr-cli_v3.11.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 Vultr published, not against what happened to arrive.

Pinned. vultr_cli_version is what gets installed, kept in a directory of its own (/usr/local/src/vultr-cli-<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 vultr-cli account info with no credentials and expects the CLI to get to "VULTR_API_KEY" - the binary, its Vultr client and its configuration lookup all ran; only the credentials were missing.

The key is an environment variable or a per-user file. The CLI reads VULTR_API_KEY or api-key from the user's config; the role never writes either.

License

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