Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Properties
label


Status

Status
colourYellowGreen
titleIn ProgressDone

DescriptionResearch spike to test the Nifi Registry as a potential system for version controlling and auto-loading Nifi flows
Due date
July 5th Showcase
Owner


...

  1. Stand up Nifi Registry
  2. Create a new bucket for testing
  3. Connect Nifi to the registry
    1. Add Trust Store and download key
  4. Create a template of the existing OpenLMIS - OpenSRP integrations and push it to the Nifi Registry
  5. Add the template to the registry
  6. Change the template and add a new version

...

titleScreenshots of steps

...

  1. Create a template of the existing OpenLMIS - OpenSRP integrations and push it to the Nifi Registry
  2. Add the template to the registry
  3. Change the template and add a new version

Challenges to this Approach

  • Nifi Registry requires separate credentials and access controls than GitHub. This will need to be maintained by the core OpenLMIS team.
  • Nifi Registry does not currently store passwords, so we need a separate mechanism for loading in passwords once the flows are loaded in.
  • The core OpenLMIS team would have to maintain a server and pay for hosting of that server.
  • Server Authorization, like what's currently setup on nifi-registry.ona.io is not supported in the Nifi registry. Instead, we need to research login groups in Nifi and the Nifi registry.