# Installer topicctl avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de topicctl pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:topicctl
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install topicctl
```

  Preuve: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#topicctl
```

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

## Faits du paquet

- **Clé du paquet:** brew:topicctl
- **Gestionnaire de paquets:** Homebrew
- **Version:** 2.0.2
- **Résumé source:** Declarative Kafka topic management
- **Page d'accueil:** <https://github.com/segmentio/topicctl>
- **Dépôt:** <https://github.com/segmentio/topicctl>
- **Dernière mise à jour:** 2026-07-26T00:51:25+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- topicctl (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 2.0.2
## Historique du projet et usages

topicctl is Segment's command-line tool for declarative Apache Kafka topic management. Its official README frames the project around applying topic changes from YAML and using a REPL to inspect brokers, topics, consumer groups, messages, offsets, partitions, ACLs, and related Kafka resources.

### Historique du projet

The project was created to make Kafka topic management more transparent and user-friendly for Segment's operational use. The README says standard Kafka tooling was tedious and error-prone for this job because it lacked a standard declarative format that could be checked into Git and required multiple commands with different interfaces to understand cluster state.

topicctl's design borrows from kubectl-style declarative operations: users keep cluster and topic definitions as YAML, run apply/check/bootstrap/rebalance style commands, and inspect cluster state interactively. The README also documents a later revamp from the v0 line to support direct cluster access without ZooKeeper and add TLS/SSL and SASL security options.

### Historique d'adoption

Its adoption niche is infrastructure teams running Kafka who want package-manager-installable tooling rather than bespoke scripts. The input package facts list both Homebrew and Nix packaging, while the official README also documents Go install, source build, and Docker image installation paths.

### Modes d'utilisation

Common usage is to store cluster configuration in cluster.yaml and topic definitions under topics/*.yaml, then use topicctl apply to create or update topics so the live cluster matches the desired files. The README's quick tour also shows topicctl repl for interactive exploration and commands such as get brokers, get topics, get partitions, get offsets, and tail.

For package-nerd workflows, topicctl is the kind of CLI that turns Kafka topic state into reviewable files: bootstrap can import existing topics into configs, check can validate config against cluster state, and apply/rebalance can be put into operational runbooks or CI-style review gates.

### Pourquoi les passionnés de paquets s'y intéressent

topicctl matters to package-focused operators because it packages a common Kafka administration pain point as a single Go CLI with declarative files, a REPL, and install paths that fit Homebrew, Nix, Docker, and go install workflows. It is most significant in Kafka/platform-engineering circles rather than as a general-purpose end-user tool.

### Chronologie

- v0 era: Older implementation preserved on the official v0 branch for users who need to revert.
- v1 era: README documents a revamp adding ZooKeeper-less cluster access plus TLS/SSL and SASL options.
- 2026: GitHub releases page lists the v2.0.x line, including v2.0.0 and v2.0.2, with ongoing changes around placement strategy and bootstrapping.

### Related projects

- The README explicitly says topicctl was inspired by kubectl and points readers to Segment's data-digger as another Kafka-oriented command-line tool.

### Sources

- <https://github.com/segmentio/topicctl#readme>
- <https://github.com/segmentio/topicctl/releases>
- source_facts.package-manager


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- narrow executable package without higher-risk signals


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

- Unix: cluster.yaml, topics/*.yaml
## Autres enregistrements de gestionnaires de paquets

- Nix - topicctl: normalized package name match | nixpkgs package indexes: pkgs/by-name/to/topicctl/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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


## Sources

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