nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Chaves <>
Subject Re: tips for flow development and version control
Date Sun, 08 Oct 2017 14:11:22 GMT
Hi Joe, thanks for the promptly reply.

I believe that what I'm looking for is really much simpler than the
versioned flows.

What I need is to be able to commit my changes after making some changes on
my flow. The template could work but it would require me to always perform
an export before committing, which is kind of nagging. can I somehow
script/automate this export?

Another possibility would be to keep the flow uncompressed instead of
storing it as tar.gz. is this possible?

Once again thanks for the help.



2017-10-06 9:07 GMT-03:00 Joe Witt <>:

> Eric,
> The current mechanism we support for this sort of thing is the
> template mechanism [1].
> However, there is a lot of effort now going into building a registry
> model for versioned flows and extensions. [2]  There has also been a
> JIRA instance launched for tracking progress of the registry itself
> [3].  In recent releases the foundations for this were put in place
> with process group hosted/scoped variables (for expression language)
> and versioned extension support.
> The template approach doesn't integrate with Git directly but you can
> build a process around that.  They are useful but there are important
> shortcomings that the registry approach will solve.  I don't know if
> there is a JIRA to have direct git integration or not yet but you
> could certainly create one if interested.
> [1]
> [2]
> Configuration+Management+of+Flows
> [3]
> Thanks
> Joe
> On Fri, Oct 6, 2017 at 7:55 AM, Eric Chaves <> wrote:
> > Hi folks, I'm starting with nifi and would like to ask for some tips
> > regarding how to best setup/manage the a project folder with multiple
> flows
> > using git.
> >
> > Do you have any tips to share?
> >
> > Cheers,
> >
> > Eric

View raw message