nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <joe.w...@gmail.com>
Subject Re: Nifi Migration
Date Mon, 16 Nov 2015 17:16:11 GMT
Naveen

You can save the flow as a template and import that.  It today has
limitations such as environmental mapping is too limited and you
should know it won't copy sensitive properties.

Another option is to copy the flow.xml.gz from the current setup into
production.

We need to do more though to make this as seamless as users would
like.  A couple of our roadmap items tackle the heart of this
challenge.  But please share your views/findings as you progress.

Thanks
Joe

On Mon, Nov 16, 2015 at 12:10 PM, Madhire, Naveen
<Naveen.Madhire@capitalone.com> wrote:
> Hi All,
>
> I’ve created the workflow with the processors in one region(say Dev), how do
> I migrate this to other region(say Prod).
> Can the whole data flow be copied into a script or something   or do I need
> to create the whole workflow again?
>
> What is the best approach, I don’t see anything related to this in the
> documentation?
>
> Thanks,
> Naveen
>
> ________________________________
>
> 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.

Mime
View raw message