# flintrock mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:flintrock
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install flintrock
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:flintrock
- **Paketmanager:** Homebrew
- **Version:** 2.1.0
- **Quellzusammenfassung:** Tool for launching Apache Spark clusters
- **Homepage:** <https://github.com/nchammas/flintrock>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- flintrock (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 2.1.0
## Projektgeschichte und Nutzung

Flintrock is a command-line tool for launching Apache Spark clusters, especially short-lived EC2 clusters for experimentation, performance testing, and automated pipelines.

### Projektgeschichte

The README explicitly positions Flintrock as a faster, better alternative to spark-ec2. Its motivation section says spark-ec2 made Spark accessible but had pain points around launch speed, missing config files, non-resizable clusters, and custom machine images.

Flintrock developed into a Python CLI with YAML configuration, subcommands for launch, destroy, login, describe, add-slaves, remove-slaves, run-command, and copy-file, and support for current Spark and Hadoop/HDFS defaults.

### Adoptionsgeschichte

The project README lists external talks, guides, and papers that used or discussed Flintrock, including a Spark Summit talk titled 'Flintrock: A faster, better spark-ec2'.

Official install guidance centers on pipx/PyPI and GitHub releases, while the README notes Homebrew as a community-supported distribution that may be out of date.

### Wie es verwendet wird

A typical workflow is to run flintrock configure, save EC2 and Spark defaults into config.yaml, launch a cluster, work on Spark, and destroy the cluster afterward.

The README recommends IAM roles for S3 access rather than copying AWS credentials to clusters, and describes Flintrock as unsuitable for permanent infrastructure or non-Spark Hadoop services.

### Warum Paket-Nerds sich dafür interessieren

Flintrock is notable in package history as a CLI that wrapped a complicated cloud data workflow into a user-level package instead of a long-lived infrastructure framework.

Its packaging story also shows the boundary between official Python application distribution and community package-manager formulas: the project points users to pipx for current releases and marks Homebrew as community supported.

### Zeitleiste

- 2016: Release v0.7.0 was published.
- 2017: Release v0.9.0 was published.
- 2020: Release v1.0.0 was published.
- 2021: Release v2.0.0 was published.
- 2023: Release v2.1.0 was published and standalone builds stopped after this line according to the README.

### Related projects

- Flintrock is directly related to Apache Spark, Hadoop/HDFS, Amazon EC2, spark-ec2, and S3A access through Hadoop.
- The README contrasts Flintrock with permanent-infrastructure tools such as Terraform, Ansible, Ubuntu Juju, Databricks, Amazon EMR, and Apache Bigtop.

### Quellen

- <https://api.github.com/repos/nchammas/flintrock/releases>
- <https://github.com/nchammas/flintrock>


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- infrastructure mutation or orchestration signal


## 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

- Linux: $XDG_CONFIG_HOME/Flintrock/config.yaml, ~/.config/Flintrock/config.yaml
- macOS: ~/Library/Application Support/Flintrock/config.yaml

## Combined YAML source

View the package source record on GitHub. [combined/flintrock.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flintrock.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph