Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install ocm

local Homebrew formula metadata

Linux

Nixverifiziert · 92%

nix profile install nixpkgs#ocm

nixpkgs package indexes · pkgs/by-name/oc/ocm/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

CLI for the Red Hat OpenShift Cluster Manager

Projektlinks

Befehle und Aliase

ocm

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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`.

Zeitleiste

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.

Quellen

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

infrastructure mutation or orchestration signal

Signale

text:cluster

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`ocm`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25

Manager-Version1.0.15

Manager aktualisiert2026-06-21

lokale DatenOK

Upstreamaktuell

neueste erkannte Versionv1.0.15

https://github.com/openshift-online/ocm-cli

OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:ocm
Version	1.0.15
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/ocm
Homepage	https://www.openshift.com/
Repository	https://github.com/openshift-online/ocm-cli
Upstream-Dokumentation	https://docs.redhat.com/en/documentation/openshift_cluster_manager/2022/html/managing_clusters/using-ocm-ocm-cli_assembly-what-is-ocm
Lizenz	Apache-2.0
Quellarchiv	https://github.com/openshift-online/ocm-cli/archive/refs/tags/v1.0.15.tar.gz
Zuletzt aktualisiert	2026-06-21T23:25:22+02:00
Pulse	updated
Build-Abhängigkeiten	go
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	ocm
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

ocm

nix profile install nixpkgs#ocm

normalized package name match
Abgeglichen nach: Ocm

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/oc/ocm/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Combined YAML source

View the package source record on GitHub.

combined/ocm.yml

Verwendete Quellen

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

ocm mit Homebrew, Nix installieren