Hello Panos,
With the 1.0.0 update, security policies were added to process groups and
controller level features. This means that there is now a difference between
creating a Controller Service (CS) which is scoped to the controller (ie. for
Reporting tasks) and creating a CS which is scoped to a process group.
So in order to create a CS that is available to all processors, just create it
in the root process group. All processors will be able to reference it since
they are all within the scope of the root group.
Joe
- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: [email protected]
On Thursday, November 17, 2016 9:11 AM, Panos Geo
<[email protected]> wrote:
<!--#yiv3337264425 P {margin-top:0;margin-bottom:0;}-->Hello all,
We are using NiFi 1.0 over http without any authentication, so all our users
are coming to NiFi as anonymous.
The problem we are having is of controller services visibility. So if we create
a controller service (say database connection) from the top right option of the
canvas, this is not visible within a group of processors. Also the contrary is
also true, if we create a controller service for a group of processors, this is
not visible to the rest of the canvas.
Is there a way to assign visibility for a controller service, e.g. set global
visibility for a service, so that we don’t have to recreate it in all the
groups of processors that need it?
As a side note, we didn't have this problem with NiFi versions before 1.0.
Many thanks,
Panos
