Configuration Automation - Ping CLI

Install and update on Linux

Ping CLI is available for Linux using multiple package managers and as a standalone binary download. Choose the installation method that best fits your environment.

  • Homebrew

  • Debian/Ubuntu (.deb)

  • CentOS/Fedora/RHEL (.rpm)

  • Alpine (.apk)

  • Manual

If you have Homebrew installed on your Linux system, you can use Ping Identity’s Homebrew tap to install Ping CLI:

brew install pingidentity/tap/pingcli

Alternatively, if you prefer to add the tap explicitly before installing:

brew tap pingidentity/tap
brew install pingcli

Download the appropriate package from the latest GitHub release and install using apt:

sudo apt-get install ./pingcli_<version>_linux_amd64.deb

Or for ARM64:

sudo apt-get install ./pingcli_<version>_linux_arm64.deb

Download the appropriate package from the latest GitHub release and install using yum or dnf:

sudo yum install pingcli_<version>_linux_amd64.rpm

Or for ARM64:

sudo yum install pingcli_<version>_linux_arm64.rpm

If you’re using dnf (Fedora 22+):

sudo dnf install pingcli_<version>_linux_amd64.rpm

Download the appropriate package from the latest GitHub release and install using apk:

sudo apk add --allow-untrusted pingcli_<version>_linux_amd64.apk

Or for ARM64:

sudo apk add --allow-untrusted pingcli_<version>_linux_arm64.apk

To install Ping CLI directly into /usr/local/bin using a single command:

RELEASE_VERSION=$(basename $(curl -Ls -o /dev/null -w %{url_effective} https://github.com/pingidentity/pingcli/releases/latest)); \
OS_NAME=$(uname -s); \
HARDWARE_PLATFORM=$(uname -m | sed s/aarch64/arm64/ | sed s/x86_64/amd64/); \
URL="https://github.com/pingidentity/pingcli/releases/download/${RELEASE_VERSION}/pingcli_${RELEASE_VERSION#v}_${OS_NAME}_${HARDWARE_PLATFORM}"; \
curl -Ls -o pingcli "${URL}"; \
sudo mv pingcli /usr/local/bin/pingcli; \
sudo chmod +x /usr/local/bin/pingcli

To install a specific version, visit the GitHub releases page and download a particular version’s binary directly.

Verify the installation

After installation, verify that Ping CLI is properly installed and accessible by checking its version:

pingcli --version

You should see output similar to:

pingcli version 1.0.0

If the command is not found, ensure that /usr/local/bin is in your system’s PATH environment variable:

echo $PATH

Upgrading the CLI binary

When you upgrade Ping CLI, your existing configuration files are automatically migrated to the new format on first run. This process is safe and includes automatic backups.

  • Homebrew

  • Debian/Ubuntu

  • CentOS/Fedora/RHEL

  • Manual

If you installed Ping CLI using Homebrew, upgrading is straightforward:

brew upgrade pingcli

Then verify the upgrade:

pingcli --version

Download the new .deb package and upgrade:

sudo apt-get install --upgrade ./pingcli_<new_version>_linux_amd64.deb
sudo yum upgrade pingcli

Or with dnf:

sudo dnf upgrade pingcli

Download the new binary from the latest GitHub release and replace the existing binary:

RELEASE_VERSION=$(basename $(curl -Ls -o /dev/null -w %{url_effective} https://github.com/pingidentity/pingcli/releases/latest)); \
OS_NAME=$(uname -s); \
HARDWARE_PLATFORM=$(uname -m | sed s/aarch64/arm64/ | sed s/x86_64/amd64/); \
URL="https://github.com/pingidentity/pingcli/releases/download/${RELEASE_VERSION}/pingcli_${RELEASE_VERSION#v}_${OS_NAME}_${HARDWARE_PLATFORM}"; \
curl -Ls -o pingcli "${URL}"; \
sudo mv pingcli /usr/local/bin/pingcli; \
sudo chmod +x /usr/local/bin/pingcli

Configuration migration

When you run Ping CLI after upgrading, the tool automatically detects the old configuration format and creates a migration plan. If you’re running interactively, you’ll be prompted to approve the migration. The CLI will:

  1. Back up your existing config file (with a timestamp, for example, config.yaml.backup.20260605T123456Z).

  2. Show you what changes will be made.

  3. Apply the migration safely (atomic write).

For non-interactive environments (CI/CD scripts), set the following environment variable to auto-approve migration:

export PINGCLI_CONFIG_MIGRATION_POLICY=yes

Then run your Ping CLI command as usual.

Uninstalling Ping CLI

  • Homebrew

  • Debian/Ubuntu

  • CentOS/Fedora/RHEL

  • Manual

If you installed Ping CLI using Homebrew:

brew uninstall pingcli
sudo apt-get remove pingcli
sudo yum remove pingcli

Or with dnf:

sudo dnf remove pingcli

If you installed Ping CLI manually:

sudo rm /usr/local/bin/pingcli

Removing configuration files (optional)

Ping CLI configuration files are stored in your user’s home directory and are not automatically removed when you uninstall the binary. To manually remove them:

rm -rf ~/.pingcli

Verify signatures (optional)

For enhanced security, you can verify the integrity and authenticity of Ping CLI downloads by checking GPG signatures and checksums.

Verify using checksum

Download the checksums.txt file from the latest GitHub release and verify your binary:

sha256sum -c checksums.txt

Verify using GPG signature

Add the Ping Identity public GPG key:

gpg --keyserver keys.openpgp.org --recv-key 0x6703FFB15B36A7AC

Then verify the artifact signature:

gpg --verify pingcli_<version>_linux_amd64.sig pingcli_<version>_linux_amd64

Next steps

Now that Ping CLI is installed, proceed to: