[ 
https://issues.apache.org/jira/browse/MINIFI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358950#comment-16358950
 ] 

Aldrin Piri commented on MINIFI-66:
-----------------------------------

[~JPercivall] Yeah, sorry, there is no specifics of what those other properties 
end up in.  The items mentioned are more figurative than suggested paths.  I 
find value in both options.

I agree that one file is simpler than two.  However, my hope is that some of 
the work that has been done on C2 protocol will make files less important.  Or, 
at the very least, allows folks to kind of set and forget "agent.yml" 
properties and then make changes to "flow.yml" properties as needed.  It is my 
opinion based on what I've seen on the mailing list and social sites, that 
those former properties are not necessarily modified too much.

I'll work to draft up a doc that suggests placement for these ideas and how 
they would be handled both from a file format and the overall C2 approach.

> 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)

Reply via email to