The RPG URL can be edited after importing to the next environment, and it should be ignored when comparing against the flow in registry so it won’t be seen as a change that needs to be committed. So although you can’t use a variable, you should still be able to version control a flow with an RPG and just update the URL after deployment with a script.
> On Oct 6, 2018, at 2:19 PM, mohammed shambakey <[email protected]> wrote: > > Hi > > Thanks, guys for your help. I ended up with building the whole RPG > programmatically every time I need to change the URL, then delete > (programmatically) the RPG at the end of the workflow > > Regards > > On Sat, Oct 6, 2018 at 4:37 AM Kevin Doran <[email protected] > <mailto:[email protected]>> wrote: > Hi, > > Can you put the remote process group outside what is versioned to NiFi > Registry? For example, if the remote process group is a sink, put everything > upstream of it in a process group and version that as the thing that moves > between environments, leaving the RPG, and the connection from the versioned > PG to the RPG, as static in each environment. (Likewise, if the RPG is the > source, put everything downstream of it in a process group that is versioned.) > > Hope this helps, > Kevin > > On 10/5/18, 20:25, "evanthx" <[email protected] <mailto:[email protected]>> wrote: > > i saw this and thought I'd reply as I have a similar issue. > > We have a staging and production cluster. I have a remote process group in > them, and have our flow backed up in the registry as that seems to be the > approved method for moving flows from staging to production. > > Since the remote process group can't be a variable, however, that means > that > we can't alter that variable between production and staging? So our > production cluster keeps trying to send data to our staging cluster. We > can > fix it, but then the Registry is out of sync. > > We don't want to change it dynamically, for clarity - we just need a way > to > version our flow using the registry. If you have any advice I would > appreciate it! > > > > -- > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/ > <http://apache-nifi-users-list.2361937.n4.nabble.com/> > > > > -- > Mohammed
signature.asc
Description: Message signed with OpenPGP
