...
Page Properties | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
- Stand up Nifi Registry
- Create a new bucket for testing
- Connect Nifi to the registry
- Add Trust Store and download key
- Create a template of the existing OpenLMIS - OpenSRP integrations and push it to the Nifi Registry
- Add the template to the registry
- Change the template and add a new version
...
title | Screenshots of steps |
---|
...
- Create a template of the existing OpenLMIS - OpenSRP integrations and push it to the Nifi Registry
- Add the template to the registry
- 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.