flyctl, Checked, And Not Updating Itself

flyctl

The Fly.io CLI (flyctl) 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 flyctl; Fly.io ships versioned releases on GitHub with a checksum file (flyctl_0.4.104_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 Fly.io published, not against what happened to arrive.

Pinned. flyctl_version is what gets installed, kept in a directory of its own (/usr/local/src/flyctl-<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 flyctl apps list with no credentials and expects the CLI to get to "no access token available" - the binary, its Fly.io client and its configuration lookup all ran; only the credentials were missing.

It updates itself unless told not to. flyctl checks for new releases and can replace its own binary; the role exports FLY_NO_UPDATE_CHECK=1 from /etc/profile.d so the version on disk is the pinned one until the role changes it, and the live test reads that back.

License

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