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 the template that all of these interactions are automatically going to take place. So it requires an extra step where the user (or your script) must explicitly enabled and start the components.
The NIFI CLI has a command "pg-enable-services" that can be used to enable all the services in a given process group. You could call this from your script like "./bin/cli.sh nifi pg-enable-service -pgid someid". On Thu, Mar 21, 2019 at 11:29 AM William Gosse <[email protected]> wrote: > > 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 processor needs to be manually enabled in Controller > Services. > > > > Is there any way to avoid this manual enablement? > > > >
