[jira] [Updated] (NIFI-2937) In TLS-Toolkit, allow users to specify separate input and output locations for client configuration settings

["Bryan Rosander (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Rosander updated NIFI-2937:
---------------------------------
    Fix Version/s: 1.1.0

> In TLS-Toolkit, allow users to specify separate input and output locations for client configuration settings
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2937
>                 URL: https://issues.apache.org/jira/browse/NIFI-2937
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Yolanda M. Davis
>            Assignee: Bryan Rosander
>             Fix For: 1.1.0
>
>
> Currently when using the tls-toolkit to generate client certificate artifacts (keystore/truststore etc) users have the option to provide the location of a configuration file that will provide the information necessary to create those items (using the "F" argument).  Another option can be used to allow toolkit to write out all of the settings generated back to the indicated input file (using the "f" argument).  For scenarios where users may want to pipe in input using stdin, vs referring to a file on disk, this is not optimal since toolkit will attempt to write out to stdin causing an error.
> To prevent this error proposing to have the "f" argument also support an output location, that is separate from the location provided with the "F" argument.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)