Continuous Integration / Continuous Deployment (CICD)
Kylo currently does not have built-in or integrated CICD. However, Kylo allows you to export both templates (along with any registered properties) and feeds thatcan then be imported to any environment.
The following approach for CICD should be incorporated:
- Build a flow in Nifi and get it configured and working in a dev instance of Nifi and Kylo as a Feed.
Once its ready to be tested export that Feed from Kylo. This export is a zip containing the feed metadata along with the categories and teiomplates used to create the feed.
Have a separate VM running Kylo and NiFi. This would be where the scripts would create, run, and test the feeds and flows.
Have a separate Script/Maven project running to instantiate this feed and run it. This could look something like the following: Have a maven module running that has a TestCase that looks for these exported feed zip files and then uses NiFi and Kylos Rest apis to create them, run the feed, verify the results, and then tear down the flow.
Kylo operates over REST and has many rest endpoints that can be called to achieve the same results as you see in the Kylo UI. For example importing a feed can be done by posting the zip file to the endpoint:
/v1/feedmgr/admin/import-feed
Once the tests all are passed you could take that exported Feed/Template, save it in a version control system (i.e. git), and import it into a different environment.
Figure 4.8 below depicts an example of an overall CICD ecosystem that could be implemented with Kylo with an approach similar to what Think Big R&D has put forward.
Figure 4.8