Automic VaultAutomic Vault

brew

apache-brooklyn-cli mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für apache-brooklyn-cli in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install apache-brooklyn-cli

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Apache Brooklyn command-line interface

Verlauf

Projektgeschichte und Nutzung

Apache Brooklyn CLI is the `br` command-line client for Apache Brooklyn, an Apache cloud application management project used to model, deploy, monitor, and manage applications across clouds and other environments.

Projektgeschichte

Apache Brooklyn's root README describes the platform as a system that supports blueprints in YAML or Java, deploys them to many clouds and target environments, monitors deployments, maintains a live model, and runs autonomic policies to keep applications healthy.

The CLI client is a separate Apache Brooklyn sub-project, written in Go. Its README says the repository contains the CLI client for Apache Brooklyn and can be built directly with Maven or inside Docker.

Official CLI docs describe `br` as a Brooklyn command-line client application. The command set covers login, deploying YAML blueprints, listing applications, reading sensors and config, invoking effectors, catalog operations, activity logs, policies, entity trees, and version checks against a running Brooklyn server.

Adoptionsgeschichte

Brooklyn's packaging history reflects a classic Apache server-plus-client split. The official docs list platform-specific CLI downloads for Windows, Linux, and OS X, and also note that the client binaries are included inside the Apache Brooklyn distribution under `bin/brooklyn-client-cli/`.

Homebrew packages only the CLI formula as `apache-brooklyn-cli`, exposing the `br` executable for users who want to operate a Brooklyn server without installing the full distribution locally.

Wie es verwendet wird

The basic workflow is `br login <URL> [username [password]]`, followed by commands such as `br deploy`, `br application`, `br catalog`, `br sensor`, `br effector`, and `br config`. The official docs note that username and password can be omitted when connecting to a localhost server with no security enabled.

The CLI is not the Brooklyn server itself. It is a remote-control tool for a running Brooklyn instance, so its package value is in scripting, automation, and inspecting cloud application state from a terminal.

Warum Paket-Nerds sich dafür interessieren

The package is interesting because it is a narrow client extracted from a larger Java-based Apache platform. Installing a small Go CLI through Homebrew gives operators the useful terminal surface of Brooklyn without pulling in the full server runtime.

It also shows the older Apache cloud-management era in package form: YAML blueprints, jclouds-style locations, application trees, effectors, sensors, catalog items, and server-side config exposed through one `br` command.

Zeitleiste

  • 2014: Apache Brooklyn NOTICE files identify Apache Software Foundation copyright beginning in 2014.
  • 2019: Official CLI reference source in brooklyn-docs records `br` command documentation metadata.
  • 2020: Brooklyn docs build metadata shows the published GitBook-era latest docs and CLI pages.

Related projects

  • Apache Brooklyn is the server and management platform controlled by the CLI.
  • Brooklyn blueprints are YAML or Java application models deployed and managed through the platform.
  • Apache jclouds-style cloud locations are part of the broader Brooklyn operating model.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 10 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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
brcliglobales 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-08
Manager-Version1.1.0
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/apache/brooklyn-client

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:apache-brooklyn-cli
Version1.1.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/apache-brooklyn-cli
Homepagehttps://brooklyn.apache.org
Repositoryhttps://github.com/apache/brooklyn-client
Upstream-Dokumentationhttps://brooklyn.apache.org/v/latest
LizenzApache-2.0
Quellarchivhttps://github.com/apache/brooklyn-client/archive/refs/tags/rel/apache-brooklyn-1.1.0.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

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.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment