nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Logan <>
Subject Re: Variable / Nifi-EL for RPG Endpoint?
Date Thu, 06 Sep 2018 20:09:41 GMT
Thanks Bryan -- Is that in terms of Docker Registry? We don't currently use
Docker Registry, but our plan was to bundle a flow.gz into a Docker image
directly. I'm not sure if maybe we're approaching this problem in a weird
way? How do most people handle multiple instances in different environments
that are disconnected from one another? We considered running a Docker
Registry container as an option, or specifying the flow.gz directly as an
option...both seem to have some issues and inconveniences.


On Thu, Sep 6, 2018 at 4:01 PM, Bryan Bende <> wrote:

> Jon,
> The RPG URL is treated similar to sensitive properties or parent
> controller services, meaning that after deploying your flow you can
> issue an update to the RPG to set the URL to given environment's value
> and that change will not be considered a change as far as version
> control and will be retained when upgrading the process group to newer
> versions.
> Thanks,
> Bryan
> On Thu, Sep 6, 2018 at 3:48 PM, Jon Logan <> wrote:
> > We are running into a slight issue when we wish to migrate between NiFi
> > cluster instances...the RPG endpoint in our flow seems to disallow
> setting
> > of a variable, which makes our flow have to be specific to the specific
> > environment it's being deployed in. It seems odd that it won't let us use
> > an expression there and set the value to a variable -- is this an
> > oversight? Is there some design decision here that we're missing?
> >
> > Thanks!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message