...
- Adds a git flow persistence provider that stores flow snapshot versions in a git repository and can be optionally configured to push changes to a remote repository such as one hosted on GitHub.
- Adds a flow hook extension point API. Write and configure your own hooks that get called any time a new flow snapshot version is saved to NiFi Registry. An included implementation can be configured to run an external script any time a new flow version is created.
Additional deployment flexibility and configuration options
An external database, such as PostgreSQL, can now be used in place of an embedded H2 database
Adds a Dockerfile for building a NiFi Registry Docker image
More options for mapping LDAP group membership of users to NiFi Registry when using LDAP security
- UI/UX refinements
- Now using NiFi Flow Design System
- Upgrades front end application to Angular 5.2
- Bucket IDs and Flow IDs are now discoverable in the UI to assist in the development of automations scripts
- Bug fixes
Flow version count updates correctly after adding a new version of a flow
Correct sorting of groups in the "Add user to groups" dialog
- REST API improvements
- A new flow "diff" endpoint returns a summary of differences between two versions of a flow
- New endpoints for interacting with flows by global id without having to specify the bucket
- New remote management endpoints (specifically, Spring Boot Actuator endpoints are available)
- A self-hosted Swagger UI to aid in development and testing
- Documentation improvements
- A new "Getting Started" quick start guide has been added to the documentation
- REST API documentation and Swagger specification corrections and additions. Documentation of each API endpoint now includes which access policies are required for each end point when NiFi Registry is secured
...