flyctl, Checked, And Not Updating Itself
flyctl on EL 10 from the GitHub release, refused by Ansible's get_url unless its SHA-256 is the one in Fly.io's checksum file, re-checked by the live test. flyctl replaces its own binary unless told not to: the role exports FLY_NO_UPDATE_CHECK=1 for every login shell. Pinned; an API call without a token stops at 'no access token available'. Original role, live-tested on Rocky Linux 10.
Verification
Live-testedReally deployed to a container sandbox, proven idempotent (a second run changes nothing), verified against the role’s assertions, then torn down.
Conformance
- Static validation (yamllint · ansible-lint)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-09-19 · podman 4.9.3 · ansible 2.21.4 · how we verify
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/ansible-flyctl?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Ansible role 1.0.0, live-tested on IaC Bazaar: [flyctl, Checked, And Not Updating Itself](https://www.iac-bazaar.com/catalog/ansible-flyctl?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```yaml
# flyctl, Checked, And Not Updating Itself: https://www.iac-bazaar.com/catalog/ansible-flyctl (download from your IaC Bazaar account)
```Preview:
Documentation
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.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Variables
- Test
Related modules
ansible-forgejo-runner
Forgejo Runner 13.2 from the vendor's release, sha256-checked, in a hardened unit, registered the way Forgejo now asks: a secret registered with forgejo-cli on the Forgejo host and a connection in config.yml. The live test pushes a workflow; its job runs on the runner and finds /home hidden, /tmp private and the system read-only. Original role, live-tested on Rocky Linux 10.
ansible-forgejo
Forgejo from the upstream release as a hardened service on loopback with sqlite and a configuration it never needs to write. The live test creates an administrator with Forgejo's own command, sees a wrong password refused and registration disabled, creates a private repository, hides it from an anonymous request and clones it over HTTP. Original role, live-tested on Rocky Linux 10.
ansible-atmos
atmos on EL 10 from the GitHub release, get_url refuses it unless its SHA-256 is the one in the vendor's SHA256SUMS, and the live test re-checks it, then writes an atmos.yaml, a stack and a component, validates the stacks and describes the component with no Terraform installed. Pinned. Original role, live-tested on Rocky Linux 10.
ansible-checkov
Checkov pinned in /opt/checkov, a virtual environment apart from the system Python. The live test runs pip check, scans a one-resource module with the built-in checks and --skip-download and expects a 'Failed checks:' summary with no network, and asserts the system Python cannot import it. Original role, live-tested on Rocky Linux 10.
ansible-conftest
conftest on EL 10 from the GitHub release, refused by Ansible's get_url unless its SHA-256 is the one in the project's checksums.txt, and re-checked with sha256sum -c by the live test, which then writes a one-rule Rego v1 policy and a one-line document, runs conftest test and expects the denial in the report. Original role, live-tested on Rocky Linux 10.
ansible-consul-cli
consul on EL 10 from releases.hashicorp.com: the client binary, not a server. HashiCorp's key lives in a GnuPG home of its own, pinned by fingerprint; the SHA256SUMS signature is verified before get_url checks the zip against that file, and the live test verifies it again, then runs consul members against nothing and expects the refused connection. Original role, live-tested on Rocky Linux 10.