Ok, I'm assuming by "flow files in git repo" you mean template XML files that you exported from NiFi and saved in Git?
I think the approach with NiFi Registry would be much better than using templates, but for what you are trying to do right now, you'll need to give some info about what the issues are... error messages, stack traces, etc. On Thu, Feb 15, 2018 at 12:18 PM, Sean Marciniak <[email protected]> wrote: > Hi Bryan, > > We are not currently using NiFi Registry. We are deploying flow files using > the restful api however, we are having issues trying do with nifi in secure > mode. > > I'm assuming you are asking how you can automate this so that you can spin > up a new cluster and then deploy a flow automatically, is that correct? > > Yeah, we currently have our flow files inside a git repo that are versions > and we are hoping to deploy from our CI/CD server. > > > The final plan is to move NiFi into a scalable Kubernetes cluster with > automated deployment of flow files. > > On 15 February 2018 at 4:56:04 pm, Bryan Bende ([email protected]) wrote: > > Hi Sean, > > Are you using NiFi Registry [1]? That should be your primary way of > deploying flows. > > I'm assuming you are asking how you can automate this so that you can spin > up a new cluster and then deploy a flow automatically, is that correct? > > If you are not talking about automation, then everything you need for a > secure setup between NiFi and NiFi Registry should already exist. > > If you are trying to do automation, then you may be interested in some of > the work we've been doing on NIFI-4839 [2]. > > Using this CLI, the starting point would be that somewhere you have the JSON > of a versioned flow from a NiFi registry, presumably from your DEV instance > where your developed everything. The JSON could be in a file, or posted > somewhere on an accessible URL. > > In your new environment, you would then do something like the following > (these are CLI commands): > > registry create-bucket -b "My Bucket" > > registry create-flow -b <bucket-id> -fn "My Flow" > > registry import-flow-version -f <flow-id> -i <file-or-url> > > nifi pg-import -b <bucket-id> -f <flow-id> -fv <version> > > nifi pg-start -pgid <process-group-id> > > Obviously this CLI is still under development and subject to change, as it > has not yet been reviewed and merged to NiFi's master branch. > > Thanks, > > Bryan > > [1] https://nifi.apache.org/registry.html > [2] https://issues.apache.org/jira/browse/NIFI-4839 > > > On Thu, Feb 15, 2018 at 10:36 AM, Sean Marciniak <[email protected]> wrote: >> >> Hi team, >> >> I am trying to figure out how best to deploy flow files to a NiFi with it >> set up in 'Secure Clustered Mode'. >> >> Any advice and examples of doing so would be greatly appreciated. Once we >> get this working, we can look at using this inside Kubernetes. >> >> I had asked inside the Hipchat room and was told to send an email instead: >> >> ``` >> [2:08 PM] Sean Marciniak: Hey team,I have a question regarding deploying >> flow files when NiFi is in secure clustered mode. >> Has this been done before? Is there a working example that you know of? >> We know we can deploy to NiFi with secure mode turned off but we require >> this to be working >> [2:12 PM] Sean Marciniak: We are trying to use NiFi v1.5 if that helps >> ``` >> Original question. >> >> Thank you, >> >> Sean. >> >> >> -- >> >> Sean Marciniak >> >> [email protected] >> >> www.beamery.com >> >> Are you ready for GDPR? GDPR: The Complete Guide for Recruiting Teams > >
