How to Install Tronador CLI

tronador-cli is the new Cloud Ops Works command-line entry point for Tronador repository lifecycle workflows, AWS resource automation, and template upgrades. This guide is extracted from the cloudopsworks/tronador-cli README and installation guide as of June 1, 2026.

What you get

• Repository template lifecycle commands under tronador-cli repos.
• Template detection, compatible tag discovery, upgrade, recovery, migration, CICD metadata, and push helpers.
• AWS resource automation for organization metadata, S3/EC2 remediation, default VPC removal, and related operations.
• Release artifacts published from the same GoReleaser pipeline: GitHub archives, Linux packages, Homebrew, Chocolatey, shell installers, and PowerShell installers.

Prerequisites

For installed binaries:

• AWS credentials with the permissions required by the tronador-cli aws ... command you plan to run.
• GitHub authentication through GH_TOKEN, GITHUB_TOKEN, or gh auth login when running tronador-cli repos commands that query GitHub or set repository defaults.

Quick install matrix

Linux and macOS shell installer

Supported targets are macOS amd64 / arm64 and Linux amd64 / arm64.

Install the latest stable release:

curl -fsSL https://raw.githubusercontent.com/cloudopsworks/tronador-cli/master/scripts/install.sh | sh

Install an explicit version. Explicit versions can point to prereleases:

curl -fsSL https://raw.githubusercontent.com/cloudopsworks/tronador-cli/master/scripts/install.sh | sh -s -- --version v1.2.3

Useful installer options:

scripts/install.sh --install-dir "$HOME/.local/bin"
scripts/install.sh --repo cloudopsworks/tronador-cli --version v1.2.3 --dry-run

Upgrade by rerunning the installer with no version for the latest stable release, or with a new explicit version.

Uninstall a shell install by removing the installed binary:

rm -f /usr/local/bin/tronador-cli
# or, if installed for the current user:
rm -f "$HOME/.local/bin/tronador-cli"

Windows PowerShell installer

Install the latest stable release:

iwr https://raw.githubusercontent.com/cloudopsworks/tronador-cli/master/scripts/install.ps1 -UseB | iex

Install an explicit version:

& .\scripts\install.ps1 -Version v1.2.3

Validate URL resolution without downloading artifacts:

& .\scripts\install.ps1 -Version v1.2.3 -Architecture amd64 -DryRun

By default, the installer writes to:

%LOCALAPPDATA%\Programs\tronador-cli\bin

It also adds that directory to the user PATH unless -NoPathUpdate is provided. Upgrade by rerunning the installer. Uninstall by deleting tronador-cli.exe from the install directory and removing the directory from the user PATH if it is no longer needed.

Native Linux packages

GoReleaser generates DEB, RPM, and APK packages from the same release binaries. Download the package matching your version and architecture from the GitHub Release assets, then install it locally.

# Debian / Ubuntu
sudo apt install ./tronador-cli_<version>_<arch>.deb

# RHEL / Fedora / CentOS
sudo dnf install ./tronador-cli-<version>-1.<arch>.rpm
# or:
sudo rpm -i ./tronador-cli-<version>-1.<arch>.rpm

# Alpine Linux
sudo apk add --allow-untrusted ./tronador-cli_<version>_<arch>.apk

The packages install tronador-cli into /usr/bin and include README/license documentation under /usr/share/doc/tronador-cli/.

Upgrade by installing a newer package from a later release. Uninstall with the platform package manager:

sudo apt remove tronador-cli
sudo dnf remove tronador-cli
sudo apk del tronador-cli

Homebrew

brew install cloudopsworks/tap/tronador-cli

Homebrew handles upgrades and uninstall:

brew update && brew upgrade tronador-cli
brew uninstall tronador-cli

Chocolatey

choco install tronador-cli

Chocolatey handles upgrades and uninstall:

choco upgrade tronador-cli
choco uninstall tronador-cli

Verify the install

tronador-cli version
tronador-cli --help
tronador-cli repos --help

A useful first repository command is version discovery for a local project:

tronador-cli repos available --workdir ../my-service

Then run an upgrade workflow with either the latest compatible tag in the current major/minor line or an explicit tag:

# Latest compatible upgrade workflow
tronador-cli repos upgrade --workdir ../my-service

# Explicit tag or branch
tronador-cli repos upgrade v5.10.12 --workdir ../my-service

Release-selection policy

• Install scripts default to the GitHub latest release endpoint, which resolves stable releases.
• Prerelease installation is allowed only when you explicitly pass a version/tag.
• Homebrew, Chocolatey, and native Linux package metadata is generated by the GoReleaser pipeline from the same archive names and checksums as the GitHub Release.