[
https://issues.apache.org/jira/browse/NIFI-10499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747587#comment-17747587
]
Greg Solovyev commented on NIFI-10499:
--------------------------------------
I implemented this on anetac's fork
https://github.com/Eng-Anetac/nifi/commit/96c8bb67fd2c481c8556c956dec2aa29afb4b3d0
> Most AWS Processors should allow Region to be specified via attribute
> ---------------------------------------------------------------------
>
> Key: NIFI-10499
> URL: https://issues.apache.org/jira/browse/NIFI-10499
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Greg Solovyev
> Priority: Major
>
> Most of the AWS Processors have a property for "Region" (e.g., us-west-2).
> The property has a set of allowable values that are provided by the SDK.
> However, often times the Region to use is unknown when the flow is developed.
> For example, when a ListS3Bucket is used, it provides in that listing what
> the Region is. But then it must be specified again in the FetchS3Object
> processor, even though it's a known attribute.
> While it's important to provide a drop-down list of allowable values, one of
> those Allowable Values should be "Use 'aws.region' attribute"
> If selected, the region should be determined by looking at the specified
> attribute.
> The ListS3 processor should also include this in its output. While it's not a
> part of the S3ObjectSummary that is returned from AWS, it is known by the
> ListS3 processor because it's configured there. For this processor, the
> region should not be able to make use of the 'aws.region' attribute, but most
> others, such as PutS3 and FetchS3 should.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
