elp it is much approceiated.
-Original Message-
From: William Gosse
Sent: Thursday, March 21, 2019 2:55 PM
To: users@nifi.apache.org
Subject: RE: Automate the Enablement of a StandardHttpContextMap
[CAUTION: This email originated from outside of Kodak Alaris. Do not click
links or o
; From: Bryan Bende
> > Sent: Thursday, March 21, 2019 12:27 PM
> > To: users@nifi.apache.org
> > Subject: Re: Automate the Enablement of a StandardHttpContextMap
> >
> > [CAUTION: This email originated from outside of Kodak Alaris. Do not click
> > links or open a
nal Message-
From: Bryan Bende
Sent: Thursday, March 21, 2019 12:27 PM
To: users@nifi.apache.org
Subject: Re: Automate the Enablement of a StandardHttpContextMap
[CAUTION: This email originated from outside of Kodak Alaris. Do not click
links or open attachments unless you recognize the sen
When a template, or a versioned flow, is instantiated, all the
processors are initially stopped and the services are disabled. This
is done on purpose since starting and enabling components may cause
interactions with external systems, and it may not be clear or desired
that just by instantiating
I'm trying to automate the deployment of a template that contains a
HandleHttpRequest processor.
My issue is that this always comes up with an Invalid component marker after a
fresh deployment of the template.
The cause of this marker is that the StandardHttpContextMap in the
HandleHttpRequest
