qubership-nifi-registry is a service built on top of Apache NiFi Registry. Compared with Apache NiFi Registry it supports:
- additional environment variables for configuration.
- configuration parameters for PostgreSQL DB storage.
- migration process for moving from file-based storage to DB storage.
- AccessPolicyProvider and UserGroupProvider for PostgreSQL with in-memory cache.
- Integration with Consul as configuration source for logging levels and other configuration properties.
qubership-nifi-registry serves as version control tool for qubership-nifi (or Apache NiFi in general). Depending on configuration, it relies on:
- externally provided TLS certificates: TLS is required for security to be enabled, so TLS certificates are need for all configurations, except may be configuration for local development
- identity provider service: required for OIDC integration, if it's enabled
- PostgreSQL DB: required, if DB storage is used. Alternative is to store data on disk with H2 DB (metadata DB), files (flow storage and users/policies information).
Build process requires the following tools:
- Java - JDK 17 or JDK 21
- Maven - Maven 3.x, see maven installation guide for details on how to install
- Docker - any version of Docker Engine or any compatible Docker container runtime.
To execute maven build, run:
mvn clean installOnce maven build is completed, you can execute Docker build. To do that, run:
docker build .Apache NiFi Registry is a service providing version control, abilities to export/import for Apache NiFi flow. Refer to Apache NiFi Registry User Guide for basic usage.
