# nifi-registry mit Homebrew installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für nifi-registry in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:nifi-registry ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install nifi-registry ``` Evidenz: local Homebrew formula metadata ## Paketfakten - **Paketschlüssel:** brew:nifi-registry - **Paketmanager:** Homebrew - **Version:** 2.11.0 - **Quellzusammenfassung:** Centralized storage & management of NiFi/MiNiFi shared resources - **Homepage:** - **Zuletzt aktualisiert:** 2026-08-03T14:50:16Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - nifi-registry (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 2.11.0 ## Projektgeschichte und Nutzung Apache NiFi Registry is a NiFi subproject for storing and managing shared resources, especially versioned NiFi flows. It is best understood as a companion service to Apache NiFi rather than a standalone data platform. ### Projektgeschichte NiFi Registry grew out of the Apache NiFi ecosystem after NiFi entered Apache from NSA's NiagaraFiles work. The Registry page describes it as a complementary application for storage and management of shared resources across one or more NiFi or MiNiFi instances. The first Registry implementation focused on versioned flows: process-group-level dataflows created in NiFi could be placed under version control, organized into buckets, and managed through Registry permissions. ### Adoptionsgeschichte Registry adoption followed NiFi teams that needed repeatable flow promotion, rollback, and collaboration. The official user guide centers on buckets, flows, versions, changelogs, import/export, user/group management, and policies. The adoption story changed with NiFi 2. The official Registry page says Apache NiFi Registry was deprecated after a February 2026 community vote and is planned for removal in Apache NiFi 3.0 because NiFi 2 introduced Git-based Flow Registry Clients for GitHub, GitLab, Bitbucket, and Azure DevOps. Homebrew's formula API reported 210 installs over 365 days, 57 over 90 days, and 22 over 30 days when queried on July 1, 2026. That smaller count compared with nifi itself fits a companion service used mainly by teams doing flow versioning. ### Wie es verwendet wird Operators used NiFi Registry to create buckets, store versioned flows, inspect the change log for saved versions, export a flow version, import a new version, and control permissions around those artifacts. In NiFi 1.x style deployments, it was the dedicated service for flow version control. Package nerds usually install it alongside nifi and nifi-toolkit for local labs or automation tests: run the Registry service, point NiFi at it as a registry client, then use either the web UI or toolkit CLI commands to import/export or promote flows. ### Warum Paket-Nerds sich dafür interessieren The interesting packaging wrinkle is lifecycle. nifi-registry packages a real historical NiFi deployment pattern, but the official project direction has moved toward direct Git-based flow registry clients in NiFi 2. That makes the formula useful context for older installations and migration work. ### Zeitleiste - November 25, 2014: NSA announces the open-source release of NiagaraFiles/NiFi through Apache. - July 20, 2015: Apache announces NiFi as a Top-Level Project. - NiFi 1.x era: Registry serves as the dedicated service for versioned flows. - February 2026: Apache NiFi Registry is deprecated after a community vote, according to the Registry project page. - Apache NiFi 3.0: Registry is planned for removal unless maintenance circumstances change. ### Related projects - Apache NiFi, Apache MiNiFi, NiFi Toolkit, GitHub Flow Registry Client, GitLab Flow Registry Client, Bitbucket Flow Registry Client, Azure DevOps Flow Registry Client ### Quellen - - - - - ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - 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: $NIFI_REGISTRY_HOME/conf/nifi-registry.properties, $NIFI_REGISTRY_HOME/conf/bootstrap.conf, $NIFI_REGISTRY_HOME/conf/identity-providers.xml, $NIFI_REGISTRY_HOME/conf/authorizers.xml ## Combined YAML source View the package source record on GitHub. [combined/nifi-registry.yml](https://github.com/mxcl/pkgdb/blob/main/combined/nifi-registry.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