Automic VaultAutomic Vault

brew

Install iceberg-cli with Homebrew

Command-line interface for Apache Iceberg. Version 0.6.0 via Homebrew; verified 2026-05-28.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install iceberg-cli

local Homebrew formula metadata

overview

Package summary

Command-line interface for Apache Iceberg

Commands and aliases

  • iceberg

history

Project history and usage

Apache Iceberg CLI is the command-line program built from Apache Iceberg Go. It gives developers a local `iceberg` executable for catalog inspection, namespace and table operations, snapshot maintenance, rollback, tagging, branch work, and JSON-friendly automation.

Project history

The CLI inherits its significance from Apache Iceberg, the open table format originally developed at Netflix and contributed to the Apache Software Foundation in 2018. Iceberg's format made table metadata, snapshots, schema evolution, hidden partitioning, and multi-engine access central to data-lake operations.

The Go implementation made Iceberg usable in Go services and small operational tools without requiring a JVM. Its CLI documentation explicitly says the command is built from `./cmd/iceberg` and that its usage is similar to PyIceberg's CLI, placing it in the growing family of non-Java Iceberg implementations.

Adoption history

The CLI reflects Iceberg adoption moving from engine-integrated libraries into packageable operational tools. The Apache Iceberg site lists Go alongside Python, Rust, and C++ as other implementations, while the Homebrew formula exposes the Go CLI directly as `iceberg`.

Its package-manager role is strongest for data engineers who want quick catalog checks, snapshot inspection, and maintenance commands from scripts, CI jobs, or a laptop shell.

How it is used

Typical use starts with a REST, Glue, Hive, or Hadoop catalog URI, optionally read from `~/.iceberg-go.yaml`. Commands cover listing namespaces, creating and describing tables, inspecting snapshots and refs, expiring snapshots, cleaning orphan files, rolling back tables, upgrading table format versions, and emitting JSON for downstream tooling.

The CLI is useful as a small operational companion to larger engines such as Spark, Flink, Trino, and Hive rather than as the primary compute engine for queries.

Why package nerds care

For package nerds, `iceberg-cli` is the small executable edge of a very large lakehouse ecosystem. It packages the Iceberg control plane as a Go binary, avoiding a JVM for routine table metadata operations.

It also shows the maturation of Apache Iceberg beyond its reference Java library: the same table format is represented by dedicated Go docs, releases, and a Homebrew formula.

Timeline

  • 2018: Iceberg was contributed to the Apache Software Foundation.
  • 2020: Apache Iceberg graduated as an Apache top-level project.
  • 2024: Apache Iceberg Go began publishing 0.x releases for the Go implementation.
  • 2026: The Go CLI documentation covers catalog flags, config files, maintenance commands, refs, branches, tags, and JSON automation.

Related projects

  • Apache Iceberg is the table format and Java reference implementation behind the ecosystem.
  • PyIceberg is the Python implementation whose CLI behavior is referenced by the Go CLI documentation.
  • Apache Iceberg Rust and C++ are sibling non-Java implementations listed by the Apache Iceberg documentation.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

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.

Unix
~/.iceberg-go.yaml

executables

Installed executables

CommandKindExposureNote
icebergcliglobal executable

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-07-08
manager version0.6.0
manager updated2026-05-28
local dataok
upstreamcurrent
latest detectedv0.6.0

https://github.com/apache/iceberg-go

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:iceberg-cli
Version0.6.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/iceberg-cli
Homepagehttps://go.iceberg.apache.org/cli.html
Repositoryhttps://github.com/apache/iceberg-go
Upstream docshttps://go.iceberg.apache.org/cli.html
LicenseApache-2.0
Source archivehttps://github.com/apache/iceberg-go/archive/refs/tags/v0.6.0.tar.gz
Last updated2026-05-28T18:47:12Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

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
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment