[ 
https://issues.apache.org/jira/browse/NIFI-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787040#comment-16787040
 ] 

ASF subversion and git services commented on NIFI-6078:
-------------------------------------------------------

Commit 79e05c9f583aa1e4d390f380e375253bd7be198e in nifi's branch 
refs/heads/master from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=79e05c9 ]

NIFI-6078: Create PostSlack processor

Processor for sending messages on Slack and optionally upload and attach
the FlowFile content (e.g. an image) to the message.

NIFI-6078: Remove username/icon properties.

NIFI-6078: Make Text property optional.

NIFI-6078: Documentation changes.

Signed-off-by: Matthew Burgess <mattyb...@apache.org>

This closes #3339


> Create PostSlack processor
> --------------------------
>
>                 Key: NIFI-6078
>                 URL: https://issues.apache.org/jira/browse/NIFI-6078
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Major
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> Implement a new PostSlack processor which is able to upload and attach the 
> FlowFile content (eg. an image) to the Slack message.
> The current PutSlack processor uses Slack Webhooks which have some 
> limitations:
> - file uploading not supported, only text messages (which can contain 
> attachment links, but not the file to be uploaded itself)
> - the current version of Slack Webhooks do not support the runtime 
> configuration of Channel, Username, etc, parameters any more, so these 
> properties of PutSlack have no effect
> To overcome these limitations, the Slack Web API needs to be used instead of 
> Webhooks. Due to this technology change, it is better to reimplement the 
> functionality in a new processor than extending the existing one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to