[
https://issues.apache.org/jira/browse/MINIFI-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045526#comment-16045526
]
marco polo commented on MINIFI-333:
-----------------------------------
I think the configuration of the client is agnostic of YAML or some other
mechanism. A client would need to ship with a "bootstrap," but it shouldn't
matter if it is minifi.properties or YAML. We should move away from thinking
chicken and egg from either configuration, in which case we could ship with
controller service implementations that are used as a precondition for a
listener.
What does "We can not cross reference the same." mean? We can reference
whatever we need to. The problem is that the listener is so coupled with flow
controller. If the listener is a controller service it will be auto started and
an be referenced from the flow controller. We might then be able to draw a
class diagram or call graph that decouples components and is agnostic of
configuration type. We should put some thought into that. It's not only
possible, but desirable.
> Explore using controller service to provide SSL to listener
> -----------------------------------------------------------
>
> Key: MINIFI-333
> URL: https://issues.apache.org/jira/browse/MINIFI-333
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
> Reporter: marco polo
> Assignee: bqiu
>
> Explore using controller service to provide SSL to listener
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
