Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/1008
Our current intentions are specific to S3, as are the implementation and
tests, so I would prefer starting with S3 alone and refactoring later if/when
there is demand for a wider option. Also, I think
Github user baank commented on the issue:
https://github.com/apache/nifi/pull/1008
Entirely up to you James.
The signer is applied AWS wide so potentially could be useful for other
non-AWS implementations of say SQS/SNS. That said the bug is only directly
affecting S3.
---
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/1008
@baank , what would you think about moving the PropertyDescriptor and the
configuration code to the AbstractS3Processor class rather than
AWSAbstractProcessor?
---
If your project is set up for it, y
