Hey Morgan, As far as documentation on the yml schema, we've attempted to document both its current state as well as the changes over time. [1]
In terms of converting the yml into a flow.xml (and nifi.properties), that is done by the ConfigTransformer. [2] I wouldn't think it would be very difficult to wrap a main around this functionality and enable command line yml -> flow.xml. It's important to realize that the yml currently only supports a subset of NiFi functionality. Also, the conversion to yml is targeting a template exported from NiFi, so it's not quite a perfect round trip for your purposes. I'm curious what kerberos isolation you're desiring. I believe that the processors that can talk to kerberized services do support specifying credentials although I'm less familiar with that functionality. If you wanted completely separate jaas configs or something, it might be easier to handle it the way you suggested, keeping functionality isolated by using completely separate instances of (Mi)NiFi. Thanks, Bryan [1] https://nifi.apache.org/minifi/system-admin-guide.html#config-file [2] https://github.com/apache/nifi-minifi/blob/master/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/util/ConfigTransformer.java On Wed, Feb 1, 2017 at 2:37 PM, Morgan, Hunter <[email protected] > wrote: > is there any internal documentation on the minifi config yaml to flow xml > conversion process? > i’d really like to leverage this code to go back and forth from yaml to > xml flows/templates. > one thing that i think is really missing from nifi is being able to > develop and version control flows/templates with normal editors and vcs. i > know the project is talking about building versioned flow repositories and > things, but some developers want to develop flow as code, and it would be > nice to have that as an option. > any feedback on these concerns? i haven’t spent enough time diving into > the minifi code to figure out how the conversion works, but i’m working on > it. if anyone can get me up to speed, and/or point me at document that > outlines it, that would be great. > > another topic is using minifi to deploy horizontally scalable and isolated > flows. this is especially important as presently there is no kerberos > credential isolation between flows in clustered nifi. as far as i can tell, > using minifi to deploy/scale/isolate flows is not something that was > intended, but it might be a useful alternative to the clustered model. > > thanks in advance > > Hunter Morgan > Data Platform Engineering > 540 391 0440 > [email protected] > > ________________________________________________________ > > The information contained in this e-mail is confidential and/or > proprietary to Capital One and/or its affiliates and may only be used > solely in performance of work or services for Capital One. The information > transmitted herewith is intended only for use by the individual or entity > to which it is addressed. If the reader of this message is not the intended > recipient, you are hereby notified that any review, retransmission, > dissemination, distribution, copying or other use of, or taking of any > action in reliance upon this information is strictly prohibited. If you > have received this communication in error, please contact the sender and > delete the material from your computer. >
