[
https://issues.apache.org/jira/browse/NIFI-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508161#comment-16508161
]
ASF subversion and git services commented on NIFI-5022:
-------------------------------------------------------
Commit 946c2fe6b3a094026c5d376676c67e7684bd18ee in nifi's branch
refs/heads/master from [~ottobackwards]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=946c2fe ]
NIFI-5022 This closes #2588. InvokeAWSGatewayApi processor
per review, simplify header building and remove new map
Per review:
- removed apache headers from 3rd party files per
https://www.apache.org/legal/src-headers.html#3party
- referenced commit/repo in notice file
- created rat configuration to account for files without headers
Signed-off-by: joewitt <[email protected]>
> Create an AWS Gateway Web API version of InvokeHTTP
> ---------------------------------------------------
>
> Key: NIFI-5022
> URL: https://issues.apache.org/jira/browse/NIFI-5022
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
> Priority: Major
>
> Currently the AWS processors are lacking support to call AWS Gateway Web Apis.
> Nifi should provide support for calling this apis, including support for all
> the same authentication methods available to the other AWS client processors.
> Since these APIs are web services, their expected use would require an
> interface more like InvokeHTTP however, than the specialized interfaces for
> the other AWS Services.
> What would be required then would be a new AWS Processor that exposed the
> same interface as InvokeHTTP, but backed by the AWS client support ( and of
> course modified to fit the differences between the OK http client and the
> Amazon client ).
> This new processor should be able to pass all the applicable tests available
> in the InvokeHttp test suite.
> The processor should also be factored in such a way as to make it possible
> for the creation of custom processors for specific apis
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
