Automic VaultAutomic Vault

brew

使用 Homebrew, Nix 安装 ocm

查看 ocm 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install ocm

local Homebrew formula metadata

Linux

Nix已验证 · 92%
nix profile install nixpkgs#ocm

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

概览

软件包摘要

CLI for the Red Hat OpenShift Cluster Manager

历史

项目历史与用法

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.

项目历史

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.

采用历史

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.

使用方式

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.

为什么软件包爱好者会关心

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

时间线

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

安全态势

风险级别:orange

infrastructure mutation or orchestration signal.

风险分类器

orange 风险 · 中 置信度 · infrastructure

原因

  • infrastructure mutation or orchestration signal

信号

  • text:cluster

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 构建元数据列出 1 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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

可执行文件

已安装的可执行文件

命令类型暴露范围备注
ocmcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-26
管理器版本1.0.15
管理器更新时间2026-06-21
本地数据OK
上游当前
检测到的最新版本v1.0.15

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

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:ocm
版本1.0.15
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/ocm
主页https://www.openshift.com/
仓库https://github.com/openshift-online/ocm-cli
上游文档https://docs.redhat.com/en/documentation/openshift_cluster_manager/2022/html/managing_clusters/using-ocm-ocm-cli_assembly-what-is-ocm
许可证Apache-2.0
源码归档https://github.com/openshift-online/ocm-cli/archive/refs/tags/v1.0.15.tar.gz
最后更新2026-06-21T23:25:22+02:00
Pulseupdated
构建依赖go
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameocm
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix95%

ocm

nix profile install nixpkgs#ocm
  • normalized package name match
  • 匹配方式: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

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • 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