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

ASF GitHub Bot commented on NIFI-5767:
--------------------------------------

Github user pvillard31 commented on the issue:

    https://github.com/apache/nifi/pull/3124
  
    Hey @andrewmlim - it looks good to me, thanks for taking care of it, it's 
going to be very useful!
    @bbende - do you think it still makes sense to keep the CLI README file? we 
don't want to remove it until 1.9.0 is released (with the doc changes) but I 
think it'd be better to keep things in one place after that. I can file a JIRA 
if you agree with it.


> Documentation of the NiFi Toolkit
> ---------------------------------
>
>                 Key: NIFI-5767
>                 URL: https://issues.apache.org/jira/browse/NIFI-5767
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Documentation & Website
>            Reporter: Pierre Villard
>            Assignee: Andrew Lim
>            Priority: Major
>
> The NiFi toolkit should have its own documentation in a dedicated page, 
> probably just under "Admin guide".
> The documentation should have a paragraph about each tool:
>  * CLI - 
> https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-cli/README.md
>  * Configuration encryption - 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encrypt-config_tool
>  * File manager - 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#file-manager
>  * Flow analyzer
>  * Node manager - 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#node-manager
>  * Notify
>  * S2S
>  * TLS Toolkit - 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#tls_generation_toolkit
>  * ZooKeeper migrator - 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#zookeeper_migrator



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to