Configuration Automation - Ping CLI

Install and update on macOS

Ping CLI is available for macOS using Homebrew and as a standalone binary download. Choose the installation method that best fits your environment. Homebrew is the recommended installation method for macOS users.

  • Homebrew

  • Manual

The easiest way to install Ping CLI on macOS is using Homebrew. Homebrew will automatically handle platform detection (Intel or Apple Silicon) and install the appropriate binary.

Install Ping CLI:

brew install pingidentity/tap/pingcli

Alternatively, add the tap explicitly first:

brew tap pingidentity/tap
brew install pingcli

To view Ping CLI’s installation details:

brew info pingidentity/tap/pingcli

If you prefer not to use Homebrew, you can download and install Ping CLI directly into /usr/local/bin using this single-line 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}"; \
mv pingcli /usr/local/bin/pingcli; \
chmod +x /usr/local/bin/pingcli

To install a specific version, visit the GitHub releases page and download the binary you need.

Verify the installation

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

pingcli --version

You should see output similar to:

pingcli version 1.0.0

Compatibility

Ping CLI is available for both Intel and Apple Silicon (ARM64) processors. Homebrew automatically detects your system architecture and installs the appropriate version.

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

  • Manual

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

brew upgrade pingcli

Then verify the upgrade:

pingcli --version

If you installed Ping CLI manually, 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}"; \
mv pingcli /usr/local/bin/pingcli; \
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

  • Manual

If you installed Ping CLI using Homebrew:

brew uninstall pingcli

If you installed Ping CLI manually:

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

Next steps

Now that Ping CLI is installed, proceed to: