[
https://issues.apache.org/jira/browse/MINIFI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358932#comment-16358932
]
Joseph Percivall commented on MINIFI-66:
----------------------------------------
Thanks for the follow-up details [~aldrin], and I think we're on the same page
regarding the long-term vision but a bit of disconnect in the interim.
I agree that there should be some separation of the "hardware/agent" config and
the flow config when looking through the lens of the Registry/higher level
agent management. At that level, we can have different portions of the config
that can be modified by the different roles (DFM vs. "hardware" admin) but how
that makes it to the agent doesn't really matter whether it's a single file or
not does it? If anything, having just one file transferred from Registry to
agent would reduce complexity.
---
A little bit of a disconnect when I was typing the response, I feel like I
remember hearing this before, but is your envisioned goal to have a "flow.yml"
and an "agent.yml" such that the "flow.yml" can be shared across all agent
types while the "agent.yml" is unique for the agent type (Java vs. C++)? If so,
I totally understand the want to separate the files and actually, utilizing
MINIFI-424, would probably make it not too difficult to do for the java agent.
We can utilize the functionality created in MINIFI-424 to populate the
nifi.properties in the ConfigTransformer by having them set in the
bootstrap.conf by default.
Lastly, yeah, I agree that MINIFI-434 is just a stopgap while we figure out
these other design decisions. Was more of a
> Migrate non-flow properties from config.yml to bootstrap
> --------------------------------------------------------
>
> Key: MINIFI-66
> URL: https://issues.apache.org/jira/browse/MINIFI-66
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Components: Agent Configuration/Installation, Processing
> Configuration
> Affects Versions: 0.0.1
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
> Priority: Major
>
> To facilitate greater ease in configuring instances, it would be helpful to
> have the config.yml be a descriptor only of processing flow with the actual
> instance process configuration (system properties, file locations, etc) being
> migrated to something like bootstrap.conf.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
