Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
The idea is to create an HTTPRecordSink that would make a POST request to a given HTTP endpoint for every record. The controller service would take in
- URL endpoint
- StandardWebClientServiceProvider
- OAuth2 Access Token Provider
- Record Writer
- Max Batch Size
The data that would be sent to the endpoint as the payload of the POST HTTP request would be the output of the writer. This is to allow potential format transformations that would be required to match the specifications of the target endpoint.
It should also be possible to add dynamic properties that would be added as HTTP attributes including sensitive ones - similar to InvokeHTTP
The potential use cases are:
- Capturing bulletins via the QueryNiFiReportingTask and automatically filing Jira(s) for each bulletin (or similar systems PagerDuty, ServiceNow, etc)
- Sending data with PutRecord processor and remove the need for splitting a flow file into many flow files made of a single record
