Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi-registry/pull/144
@bbende This is really cool! I was able to:
1. Setup two NiFi Registry environment using the same remote Git
repository, but different branches, dev and prod.
2. Create new flow versions at dev and push it to remote origin/dev branch
3. Merge commits to origin/prod branch. Then remove database dir at prod
environment to generate it from updated Git commits.
4. After restarting the prod NiFi Registry, I can import the new flows from
dev to prod environment.
5. Updating existing flow scenario also worked. Even if I restored database
from Git commits, NiFi was able to keep notice new version and change the
deployed PG to a new version.
Haven't looked at the detail of implementation, but from functional point
of view, I'm a huge +1! Great job!
---
