We made our initial capability available but we still have more work to go to reach the full vision of that feature proposal/vision as well as related visions for extensions and flow versions.
On Fri, Mar 24, 2017 at 1:02 PM, Matt Foley <ma...@apache.org> wrote: > Hi Joe, > The specification document in the wiki is written in future tense, but is it > in fact what got implemented in the two jiras (all linked below)? > Thanks, > --Matt > > On 3/24/17, 5:50 AM, "Joe Witt" <joe.w...@gmail.com> wrote: > > James, > > In NiFi 1.x line we introduced the variable registry concept for > exactly this purpose. Right now it reads from a properties file but we > intend to also grow this to support other more dynamic/central > options. > > https://issues.apache.org/jira/browse/NIFI-2208 > https://issues.apache.org/jira/browse/NIFI-2449 > https://cwiki.apache.org/confluence/display/NIFI/Variable+Registry > > Thanks > JOe > > On Fri, Mar 24, 2017 at 8:47 AM, James McMahon <jsmcmah...@gmail.com> > wrote: > > I would like to allow my workflow administrators to control NiFi > attribute > > and configuration parameters using an editable configuration text file > read > > in at start up - similar to nifi.properties. How can I do this? > > > > An example would be the hostname and port for our AMQP broker, or for > > HandleHttpRequest. -Jim > > > >
