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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
