You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Mariama Barr-Dallas <mb...@gmail.com> on 2016/07/29 14:37:02 UTC
StandardSSLContextService Not Being shown
Hello,
I am attempting to add a Controller Service to a processor property via the
rest API by changing the descriptors field and the properties field to the
correct Id of the controller Service for the ProcessorEntity before
uploading it;
For some reason the first step is giving unexpected results: I cannot
access any of the controller services via a GET rest api call until all of
the other components (processors, process groups, connections) are loaded.
Is there a certain order to when context services can be accessed and
applied to a processor via the rest api?
Re: StandardSSLContextService Not Being shown
Posted by Bryan Bende <bb...@gmail.com>.
Hello,
Adding the dev alias as well to see if anyone else knows the answer.
-Bryan
On Fri, Jul 29, 2016 at 10:37 AM, Mariama Barr-Dallas <mbarrdallas@gmail.com
> wrote:
> Hello,
> I am attempting to add a Controller Service to a processor property via
> the rest API by changing the descriptors field and the properties field to
> the correct Id of the controller Service for the ProcessorEntity before
> uploading it;
> For some reason the first step is giving unexpected results: I cannot
> access any of the controller services via a GET rest api call until all of
> the other components (processors, process groups, connections) are loaded.
> Is there a certain order to when context services can be accessed and
> applied to a processor via the rest api?
>
>
Re: StandardSSLContextService Not Being shown
Posted by Bryan Bende <bb...@gmail.com>.
Hello,
Adding the dev alias as well to see if anyone else knows the answer.
-Bryan
On Fri, Jul 29, 2016 at 10:37 AM, Mariama Barr-Dallas <mbarrdallas@gmail.com
> wrote:
> Hello,
> I am attempting to add a Controller Service to a processor property via
> the rest API by changing the descriptors field and the properties field to
> the correct Id of the controller Service for the ProcessorEntity before
> uploading it;
> For some reason the first step is giving unexpected results: I cannot
> access any of the controller services via a GET rest api call until all of
> the other components (processors, process groups, connections) are loaded.
> Is there a certain order to when context services can be accessed and
> applied to a processor via the rest api?
>
>