Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/2628
Spoke with @alopresto offline. He highlighted that is it important to
maintain control of location of secure-hash.key file in order to prevent
calling application from piping into a file that
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/2628
@alopresto ran through test cases and this works as expected. One question
for you is there a way to designate an output location for the secure-hash.key
file? Such as if I want to pipe it to
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/2628
@alopresto thanks for addressing this, happy to review. It does look like
Travis is failing on a ratcheck related error in nifi-toolkit-encrypt-config
---
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2628
Here are some instructions and expected outputs to demonstrate that the
tool works as intended:
```
# CD to $NIFI_HOME/conf because secure_hash.key must be written to
immediate
