Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/1186
@alopresto re-ran the unit tests and scenarios looks good
+1
---
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
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1186
@YolandaMDavis I believe I have resolved the issue you were encountering,
and the unrelated test failure was due to DNS settings on my machine which I
have now fixed. Please perform the review.
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1186
@YolandaMDavis made a good catch; the tests are ambivalent in regards to
JCE jurisdiction policy, but some of the test resources I generated relied on
256-bit keys and so were not compatible with
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/1186
@alopresto just to add clarity on unit test failures, I am specifically
receiving a problem when running the ConfigEncryptionToolTest. Several tests
are failing for me and the failure appears
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/1186
@alopresto I also received problems running unit test but confirmed that I
could migrate keys using several scenarios:
raw key -> raw key
password -> password
password -> raw
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/1186
@alopresto happy to review (understanding this is WIP)
---
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
