[cetic/helm-nifi] Support NiFi Registry container for flow versioning

[jdesroch]

Is your feature request related to a problem? Please describe. I would like to enable NiFi flow version control and allow new NiFi clusters to easily pull in existing flows from other environments.

Describe the solution you'd like Have the option to spin up a apache/nifi-registry container

• Use the same security/authentication configuration as NiFi
• Configure users/permissions between the applications (proxy, read, write)
• Configure the registry client in the NiFi controller using the NiFi API call to /controller/registry-clients
• Optionally configure a remote git repo to be cloned on the container and used by the GitFlowPersistenceProvider

Describe alternatives you've considered This could be a separate chart. But the benefit of keeping them together is a single security configuration applied consistently and the potential for no configuration in the NiFi UI before getting started.

Additional context The ultimate goal is to use the NiFi Toolkit and/or NiFi & Registry APIs driven by Kubernetes configuration to allow deployment of a specific version of a NiFi flow developed in a separate environment with no user interaction.

[alexnuttinck]

Hello @jdesroch,

Thanks for your feature request! I think it should be really an improvement with we have the possibility to deploy a apache/nifi-registry with Helm on a Kubernetes cluster.

I agree threre are pros & cons to deploy the nifi registry in this repo or in a separate repo. There is another benefit if we create a seperate chart: in the case you want to deploy Nifi registry with minifi. But I agree the automatic part is nice.

If you want to make a first PR, don't hesitate.

[alexnuttinck]

58 implements this feature request.

[alexnuttinck]

Added in 0.5.0 release.