Re: Connecting Controller Services Automatically

I have put together a bug on NiFi and added steps to reproduce with a simple template. https://jira.apache.org/jira/browse/NIFI-7489 -Eric On Mon, May 25, 2020 at 10:28 AM Eric Secules wrote: > Thanks for the link Mark, > > I have found out that my problems are caused by this `continue` [1]. I

Re: Connecting Controller Services Automatically

Thanks for the link Mark, I have found out that my problems are caused by this `continue` [1]. I noticed the following state when I stopped the debugger at [1]. At this moment it's importing a versioned flow (PG C) inside a versioned flow (NiFi Flow --> PG A --> PG B --> PG C). The issue is that

Re: Connecting Controller Services Automatically

It should be hierarchical. The Set of Controller Services to match by name is obtained by calling `parentGroup.getControllerServices(true)` where parentGroup is the Process Group that components are to be added to. @Eric, the code that does the matching can be found at [1]. Thanks Mark [1]

Re: Connecting Controller Services Automatically

Do you have any controller services in process groups above the “controller container”? I can’t remember if it is based on only the immediate parent, or the entire hierarchy. On Sat, May 23, 2020 at 8:00 PM Andrew Grande wrote: > Maybe something is going on with specific types or hierarchies.

Re: Connecting Controller Services Automatically

Maybe something is going on with specific types or hierarchies. I've noticed DefaultSslContext didn't get assigned, even though it was the only one available. Does autowiring logic apply to this one? Andrew On Sat, May 23, 2020, 3:54 PM Eric Secules wrote: > Hi Bryan, > > I have noticed this

Re: Connecting Controller Services Automatically

Hi Bryan, I have noticed this behaviour sometimes, but not all the time I am running the latest registry and NiFi versions. I haven't found a conclusive pattern but I have a hunch that it has to do with having versioned process groups within versioned process groups. My deployment strategy is

Re: Connecting Controller Services Automatically

Yes, I should have clarified this. Thanks Bryan. This is the solution for the generic use case. The original question was about reducing the controller to only a single instance of a specific controller service implementation, which is how the tangent got started. Andy LoPresto

Re: Connecting Controller Services Automatically

If you use registry >= 0.5.0 And nifi >= 1.10.0, then it will auto select external controller services with the same name as long as there is only one of the same type with same name (name is not unique). On Sat, May 23, 2020 at 3:34 PM Andy LoPresto wrote: > My position is that we don’t claim

Re: Connecting Controller Services Automatically

My position is that we don’t claim completely automated deployment as a feature, so manually setting the controller service IDs is not exposed. Technically, they are defined in the flow.xml.gz and could be modified by an administrator to be static after generation. This would require frequent

Re: Connecting Controller Services Automatically

Aren't those IDs generated? How can one enforce it? Andrew On Sat, May 23, 2020, 10:53 AM Andy LoPresto wrote: > If you want the process to be completely automated, you would have to > enforce the controller service IDs to be identical across environments. > Otherwise deployment would need a

Re: Connecting Controller Services Automatically

If you want the process to be completely automated, you would have to enforce the controller service IDs to be identical across environments. Otherwise deployment would need a manual intervention to reference the specific controller service in the proper component. Andy LoPresto

Re: Connecting Controller Services Automatically

Hi Andy, Given that you have a flow which operates on two different S3 accounts for example, how would you do deployment automation? Do you mandate that the controller service with the same ID must exist in both a development and production environment rather than try to connect a processor to a

Re: Connecting Controller Services Automatically

Eric, I can’t answer all these questions but I would definitely have hesitations around building an expectation that there is only one instance of any given controller service type in an entire canvas. I can think of numerous flows (this may not affect your particular flows, but the concepts

Connecting Controller Services Automatically

Hello everyone, I am running into an issue with automated deployment using nipyapi . We would like to be able to pull down flows from a registry and have them ready to go once all their controller services have been turned on. But there are a few issues.