pkg.sopackage field notes

brew / rank 4729

Install ocm with Homebrew

CLI for the Red Hat OpenShift Cluster Manager. Version 1.0.15 via Homebrew; verified 2026-07-27.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install ocm

provider-native install command

overview

Package summary

CLI for the Red Hat OpenShift Cluster Manager

Commands and aliases

  • ocm

history

Project history and usage

OCM CLI is the command-line client for Red Hat OpenShift Cluster Manager. It gives administrators and automation scripts a direct interface to the OCM API at api.openshift.com.

Project history

The upstream openshift-online/ocm-cli README describes the project as command-line tools that simplify use of the OCM API. It is written and distributed as a Go CLI, with installation paths through Fedora/CentOS Copr packages, Homebrew, GitHub release binaries, and Go tooling.

The CLI follows the service model of OpenShift Cluster Manager: a managed service on Red Hat Hybrid Cloud Console used to create, operate, and upgrade OpenShift clusters. Red Hat documentation positions OCM as a unified dashboard for OpenShift Container Platform, OpenShift Dedicated, and Red Hat OpenShift Service on AWS cluster workflows.

The CLI evolved around authenticated API access. Its README documents offline access token login, OpenID token exchange through sso.redhat.com, per-user configuration files, `OCM_CONFIG` for multiple concurrent logins, keyring storage, opaque-token support, and raw API-style `get` requests.

Adoption history

OCM CLI adoption is tied to Red Hat OpenShift operations rather than general Kubernetes administration. It complements the OpenShift `oc` CLI: `oc` manages cluster and application resources, while `ocm` speaks to Red Hat's cluster-manager APIs for subscription, fleet, and managed-cluster workflows.

Homebrew's formula API generated on 2026-07-01 lists stable version 1.0.15 and 620 installs over 365 days. The README's Fedora/CentOS Copr path and release-binary installation instructions show that Homebrew is only one of several distribution channels for OpenShift operators.

How it is used

A user logs in with an OpenShift Cluster Manager offline token from console.redhat.com, after which credentials are stored in an OCM configuration file or supported OS keyring. Commands can then retrieve objects, query cluster collections, print tokens for use with curl, and interact with API resources under paths such as `/api/clusters_mgmt/v1/clusters`.

The CLI is especially useful for operators who need repeatable cluster-management tasks, support workflows, or scripting against api.openshift.com without manually driving the web console.

Why package nerds care

OCM CLI is a vendor operations CLI with service-specific authentication, multiple native distribution channels, and a clean Homebrew formula. Its metadata helps distinguish Red Hat's cluster-manager API tooling from the separate OpenShift client binary `oc`.

Timeline

  • The README's installation example references release v0.1.30, reflecting the pre-1.0 release series used for binary distribution.
  • Before version 0.1.56, the README says the configuration file used `~/.ocm.json`; later versions use platform-specific application configuration paths.
  • 2026-07-01: Homebrew formula metadata lists stable version 1.0.15 and 620 installs over the previous 365-day analytics window.

Related projects

  • Related projects include Red Hat OpenShift Cluster Manager, the OCM API, openshift-online/ocm-sdk-go, openshift-online/ocm-api-model, Red Hat Hybrid Cloud Console, and the OpenShift `oc` client.

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • infrastructure mutation or orchestration signal

Signals

  • text:cluster

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
~/.config/ocm/ocm.json
macOS
~/Library/Application Support/ocm/ocm.json

Credential files

Credential-bearing paths to review before unattended agent runs.

Linux
~/.config/ocm/ocm.json
macOS
~/Library/Application Support/ocm/ocm.json

executables

Installed executables

CommandKindExposureNote
ocmexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version1.0.15
manager updated2026-07-27
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:ocm
Version1.0.15
Package managerHomebrew
Homepagehttps://www.openshift.com/
Repositoryhttps://github.com/openshift-online/ocm-cli
Last updated2026-07-27T23:46:50+02:00
Pulseupdated
Bottlenot recorded
Servicenone declared

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation