[
https://issues.apache.org/jira/browse/NIFI-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606037#comment-15606037
]
ASF GitHub Bot commented on NIFI-2937:
--------------------------------------
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/1158
Was able to test toolkit successfully with following scenarios:
a) Run with both -F -f flags (allowing single file reference for
input/output) to ensure backwards compatibility
./tls-toolkit.sh client -F -f /Users/ydavis/dev/tools/certs/certconfig.json
b) Run with -f and --configJsonIn flag with both input/output referencing a
physical file (e.g. for output file is expected to be created)
./tls-toolkit.sh client -f /Users/ydavis/dev/tools/certs/output.json
--configJsonIn /Users/ydavis/dev/tools/certs/certconfig.json
c) Run with -f and --configJsonIn flag with input/output referencing
/dev/stdin and /dev/null respectively. Configuration file was piped into stdin.
cat /Users/ydavis/dev/tools/certs/certconfig.json | ./tls-toolkit.sh client
-f /dev/null --configJsonIn /dev/stdin
+1
Will merge into master.
> 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
>
> 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)
